Title: Allocation failed in SAP HANA: Need to allow long-running query to complete without memory er

[seyfeddine]

Hello SAP Community,

I’m encountering the following error when executing a stored procedure in SAP HANA Cloud:

line 79 col 11 (at pos 3216): Allocation failed; Reason: booked memory limit reached (SAP Note 3191224

I've already increased:

• statement_memory_limit

• global_allocation_limit

But the issue persists.

Context:

• The error is caused by a single query inside the procedure that performs a complex join and computation.

• The rest of the procedure runs fine — only this one query consumes excessive memory and causes the procedure to fail.

• I am not concerned about performance — I just need this query to run successfully even if it takes time.

---

My Questions:

1. Is there a way to allow long-running queries to continue even if memory usage is high — without the procedure being terminated?

2. Are there specific settings, resource group configurations, or query-level coding practices that can:

   • prevent the query from hitting allocation limits, or

   • make it fail gracefully without rolling back the entire transaction?

---

What I’ve tried:

• Increased memory-related settings via SQL and HANA Cockpit

• Refactored some logic (batching, temp tables), but this particular query still crashes

Any guidance on how to make HANA more tolerant of memory-intensive operations or tips to isolate and stabilize heavy queries would be greatly appreciated.

Thanks in advance!

---

Let me know if you want me to attach code snippets or EXPLAIN PLAN output to this message too.