3749684 - [RESOLVED] Replication flow fails due error 129 allocation failed: booked memory limit reached

Transferring data via Replication Flow failed due to the following error: Repository Error: Executing Statement List, Repository Error: SQL Error 129 - transaction rolled back by an internal error: Allocation failed; Reason: booked memory limit reached (SAP Note 3191224) (statement no: 0).

• SAP Datasphere

1. Open the Data Integration area in the affected space.
2. Go to the Replication Flow Monitor and select the replication flow that processes delta data.
3. Review the failed run details and error log; observe SQL Error 129 with “Allocation failed; Reason: booked memory limit reached”.

Last update on May 7th, 5:30PM UTC:

After internal adjustments, the memory situation was reestablished. 
SAP Development team will proceed with root cause analysis, and once performed this KBA will share the final statement.

The solution of this issue is currently under investigation.
Follow this KBA for updates.

• SAP Note 3191224 - Understand the reason for SQL statements terminating with an "Allocation failed" error message in SAP HANA Cloud
• Set priorities and statement limits for spaces or groups

sql 129, allocation failed, booked memory limit reached, replication flow, delta transfer, datasphere, hana cloud, executing statement list, repository error, transaction rolled back, memory allocation, intermittent failure, cds extraction, abap source, replication failure , KBA , DS-DI-RF , Replication Flow Runtime , Known Error