Error -129 or -128 when reloading app. This error appear after a reload of a large amount of data.
2018-05-25 11:23:25 -129 =
2018-05-25 11:23:49 Execution Failed
2018-05-25 11:23:49 Execution finished.
Other errors that may be seen when executing reload script and running out of memory resources include:
Data profiling could not be completed
The following error occurred:
-128
In the Engine audit and system logs:
Command=Reload app;Result=-128;ResultText=Error: Internal error
-129 or -128 are most frequently caused by resource constraints; the system is out of memory.
Resolution:
- Review the application to optimize it*
- Schedule the task at different times (if a scheduled task is failing that otherwise functions when run manually)
- Scale out, allowing for a dedicated reload node
- Add additional resources
* While increasing resources is of course an option, the application can be reviewed to ensure it has been optimized. One possible action to take for example is to remove the synthetic keys that are not useful to the data model.
Synthetic keys aren't always the root cause when something goes wrong but it can be hard to foresee what the impact might be. Therefore, always make sure that synthetic keys are removed from the data model.
The engine may end up using an excessive amount of time and/or memory when the number of composite keys/Synthetic Tables increases, depending on data amounts, table structure and other factors. Unfortunately, the actual limitations are virtually impossible to predict, which leaves only trial and error as a practical method to determine them.
For more information about Synthetic keys:
Best Practice for Synthetic keys/Synthetic Tables
FAQ: Why should synthetic keys be removed from QlikView applications?
Environments:
Qlik Sense Enterprise on Windows
Qlik Sense Desktop
