- An out of memory event happened in the HANA database and an oom trace file was created containing the information below:
OUT OF MEMORY occurred.
Failed to allocate <memoryvalue> Allocation failure type: OPERATING_SYSTEM_LIMIT
- The oom trace file also contains the messages below:
This is a configuration problem of your operating system:
Please increase /proc/sys/vm/max_map_count
At most one OOM dump is written in approximately Xs.
- You also see the following messages in the traces of the HANA service that reported the out of memory event:
<timestamp> e Memory Precharge.cpp(00162) : memAllocSystemPages failed with rc=12, 12 (Cannot allocate memory)
- You could also get an error similar to:
SQL submitted to ODBC data source <HANA SID> resulted in error <[SAP AG][LIBODBCHDB SO][HDBODBC] General error;2048 column
store error: search table error:  Memory allocation failed;exception 1000002: Allocation failed ; $size$=25315874691;
$name$=Pool/JoinEvaluator; $type$=pool; $inuse_count$=16; $allocated_size$=27891692375; $alignment$=8;
- BW DSO activation fails with below errors:
"Message text transaction rolled back by an internal error: fail ed to activate dso with persisted changelog: [410 02] column store error and "Message text Serious error occurred: column store error: search table error:  general error (no further information available) at ptim"
SAP HANA, platform edition
SAP HANA, platform edition, sap_hana, database, db, saphana, oom, out-of-memory, out-memory, out memory, operating_system_limit, rc=12, hdbindexserver, hdbscriptserver, hdbnameserver, hdbcompileserver, allocationlimit, global_allocation_limit, memorymanager , KBA , HAN-DB-ENG , SAP HANA DB Engines , Problem
About this pageThis is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP ONE Support launchpad (Login required).
Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.