[nQSError: 46168] Operation RawFile::checkSoftLimit failed

You can get the [nQSError: 43119] Query Failed: [nQSError: 46168] Operation RawFile::checkSoftLimit failed, it'll exceed the current limitation. 1073758528 error if the BI query requires more temporary space to complete the request than the BI Administrator has allocated.

To resolve this issue:

1. Modify the query to reduce the volume of data that is processed by the BI Server by:
   1. Adding additional filters to the query.
   2. Replacing the most detailed attribute columns with less detailed columns to reduce the overall level of detail of the query.
   3. Removing attribute columns containing long text values.
   4. Avoiding the use of SQL functions that are not supported by the backend data source.
   5. Removing certain attribute or measure columns that cause more complex internal processing in the BI Server.
2. If you cannot resolve the issue by modifying or restructuring the query and if the system is capable of handling more load, request the BI Administrator to increase the maximum size allowed for temporary files by modifying the following parameters in the NQSConfig.INI file:
   • WORK_DIRECTORY_SIZE_GLOBAL_LIMIT or
   • MAX_WORK_FILE_SIZE_PERCENT
   For example:

   [General]
   WORK_DIRECTORY_SIZE_GLOBAL_LIMIT = 100 GB;
   # No temporary file will be allowed to exceed this percentage of the global work
   # directory limit.
   MAX_WORK_FILE_SIZE_PERCENT = 5;
   

   Note:

   • The maximum size allowed for any single temporary file is determined by multiplying the total size limit of the temporary directory set in the WORK_DIRECTORY_SIZE_GLOBAL_LIMIT parameter by the percentage specified in MAX_WORK_FILE_SIZE_PERCENT. By default the temporary file size limit is 100 GB * 5% = 5 GB. This per-file limit applies to each temporary file individually, while the total WORK_DIRECTORY_SIZE_GLOBAL_LIMIT applies collectively to all the temporary files created by the BI Server.

   • You must increase the MAX_WORK_FILE_SIZE_PERCENT parameter cautiously. Setting a large percentage can allow a single request to consume a large portion of the total temporary space, possibly causing the system and other BI requests to run out of temporary space and fail. Increasing the WORK_DIRECTORY_SIZE_GLOBAL_LIMIT is safer as long as there is sufficient disk space. However, you must observe caution while increasing the value of the WORK_DIRECTORY_SIZE_GLOBAL_LIMIT parameter. Setting a large value can cause the system to run out of disk space or allow BI requests to consume too many system resources.