3507199 - 'booked memory limit reached' error in SAP Datasphere

Symptom

When trying to execute a table data replication in SAP Datasphere, the following error appears:

{"correlationId":"XXXXXXX","errorMessage":"SQL error 129: transaction rolled back by an internal error: \"XXXXX$XXXXX\".\"XXXXXXX\": line 790 col 7 (at pos 30682): \"PXXXXXX\".\"XXXXXXXXX\": line 160 col 7 (at pos 4888): Allocation failed; Reason: booked memory limit reached (SAP Note 3191224)

Environment

SAP Datasphere

Cause

The error occurs when the Data Provisioning Agent (DP Agent) system is reaching still the memory limits (not due to error, but to amount of data and computing effort involved).

Resolution

To solve the issue, you can check the part 'Allocation failed; Reason: booked memory limit reached' of the SAP Note 0003191224 - Understand the reason for SQL statements terminating with an "Allocation failed" error message in SAP HANA Cloud.

You also need to consider certain measures, i.e.

Data Provisioning Agent (DP Agent) memory requires upgrade. For further details you can use the SAP KBA 0002737656 - How to increase DP Agent memory;
Use more partitions;
Parallel processing (for e.g. 1-2 max) if the data is huge;
Ensure that the Data Provisioning Agent (DP Agent) is not running with high memory always.

All the steps above can also be checked in SAP Note 3507199 - FAQ: SAP HANA Memory
Note: If a SAP Case needs to be created (after all the checks above) you should use the component HAN-DP-SDI-DS.

Keywords

Memory, DP, Agent, Blocked, Allow, HANA, S4, On, Premise, DS, Data, Sphere, Datasphere, OOM, Performance, Replication, Flow, Data, Error, Issue, Limit, Booked, Limited , KBA , DS-DI-CON , Connections , HAN-DP-SDI-DS , SAP Datasphere specific SDI issues , HAN-DP-SDI , SAP HANA smart data integration (SDI) , Problem

Product

SAP Datasphere all versions

Attachments

Pasted image.png