Symptom
HANA database failed to start after changing global_allocation_limit to a smaller value, nameserver run out of memory during start up.
daemon trace:
====================
[397250]{-1}[-1/-1] <timestamp> i Daemon RunningInstance.cpp(00260) : Start 'hdbnameserver' as process <pid>, process group <pid>, instance 0 of <HDB Nameserver>
............
............
[397250]{-1}[-1/-1] <timestamp> i Daemon DaemonHandle.cpp(00335) : Process 'hdbnameserver', pid <pid> exited normally with status 5
[397250]{-1}[-1/-1] <timestamp> i Daemon DaemonHandle.cpp(00367) : Program 'hdbnameserver' failed during startup. Service is essential, shutting down all instances
=====================
nameserver.rtedump.<timestamp>.oom.trc:
=====================
[MEMORY_OOM] Information about current out of memory situation:
OUT OF MEMORY occurred.
Host: <hostname>
Executable: hdbnameserver
PID: <pid>
Failed to allocate 1.26gb (1362911232b).
Allocation failure type: GLOBAL_ALLOCATION_LIMIT
=====================
However, even after reverting /usr/sap/<sid>/HDB<instance number>/<host name>/global.ini >global_allocation_limit to 0, HANA still can not start up, failed with same error.
Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental.
Read more...
Environment
- SAP HANA Platform Edition 1.0
- SAP HANA Platform Edition 2.0
Product
Keywords
global_allocation_limit, nameserver, OOM, out of memory, start up, HDB Daemon not running , KBA , HAN-DB-ENG , SAP HANA DB Engines , 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.