SAP Knowledge Base Article - Preview

3545656 - HANA DB can't be started after migration due to OOM

Symptom

After HW migration, HANA database can't be started.
In indexserver trace there is information as following:
GLOBAL_ALLOCATION_LIMIT (GAL) = 13.69gb (14707552256b), SHARED_MEMORY = 3.35gb (3608027136b), CODE_SIZE = 3.03gb (3257851904b), NVM_ALLOCATED_SIZE = 0b, OOM_RESERVATION_ALLOCATOR_SIZE = 96.14mb (100810752b)
PID=2046 (hdbindexserver), PAL=13.82gb (14841769984b), AB=4.56gb (4896976896b), UA=0, U=4.44gb (4773462275b), FRO=0b, FSL=0b, FMC=0b
[Some processes may have been skipped]
Total allocated memory= 13.82gb (14847606784b)
Total used memory     = 13.25gb (14236920111b) 


Read more...

Environment

SAP HANA database

Product

SAP HANA 1.0, platform edition ; SAP HANA, platform edition 2.0

Keywords

  • GLOBAL_ALLOCATION_LIMIT
  • OOM
  • Out of memory
, KBA , HAN-DB-ENG , SAP HANA DB Engines , HAN-DB , SAP HANA Database , 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.