Symptom
- A View persistency fails with the "cannot allocate enough memory" error or "Possible reasons could be: restart of server due to some technical issues, lost database connection, an exception in a remote source etc.", when the job starts through a Task Chain.
- When executed individually, the data gets persisted without errors.
Environment
- SAP Datasphere
Reproducing the Issue
- Access the affected SAP Datasphere tenant;
- Add the Graphical View into a Task Chain;
- Run the Task Chain through the Data Integration Monitor;
- The load will fail and stop when persisting the View that you added in step 2.
Cause
- Design issue and/or performance issue due to other competing tasks.
Resolution
The possible workarounds are:
- Add more partitions to the affected View, more information in SAP Help Portal Documentation: Creating Partitions for Your Persisted Views
- OR
- Check the configured Run Mode option and test the behavior with the other mode selected (Performance-Optimized or Memory-Optimized), more information in SAP Help Portal Documentation: Data Persistence and Processing Mode.
Note: this might not work and is heavily dependent on the size of the dataset that is being processed.
See Also
SAP Help Portal Documentations:
Keywords
failed,persist, graphical, view, task chain, Cannot allocate enough memory, error, job, data integration monitor, execute, individually, Performance-Optimized, Memory-Optimized , KBA , DS-DI-SCH , Scheduling and Task Chains , Problem
Product
SAP Datasphere all versions