Symptom
- A composite limit Out of Memory (OOM) error occurs, but the memory threshold reported in the dump is lower than the globally configured
statement_memory_limit - The
compositelimit_oomdump showsAllocation failure type: STATEMENT_MEMORY_LIMIT_FROM_USER_PARAMETER, indicating the failure originates from a user-level parameter, not the global setting.
Example dump excerpt:
[MEMORY_LIMIT_VIOLATION] Information about current memory composite-limit violation:
Composite limit violation (OUT OF MEMORY) occurred.
Composite limit=100GB (107374182400B)
Root allocator name=Connection/<connection_id>/Statement/<statement_id>
MemoryType: NearDRAM
Host: <hostname>
Executable: hdbindexserver
PID: <pid>
Failed to allocate 141.12MB (147981952B).
Allocation failure type: STATEMENT_MEMORY_LIMIT_FROM_USER_PARAMETER
Read more...
Environment
SAP HANA, platform edition 2.0
Product
SAP HANA, platform edition 2.0
Keywords
HANA, composite, composite limit, out of memory, OOM, statement memory limit, user parameter, allocation failure, STATEMENT_MEMORY_LIMIT_FROM_USER_PARAMETER, global statement_memory_limit, ALTER USER, SYS.USER_PARAMETERS , KBA , HAN-DB-PERF , SAP HANA Database Performance , Problem
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.
SAP Knowledge Base Article - Preview