The following errors related to OOM are found:
Reason for shrink: Adjust NVM memory size XXXXXXXXX
Out of memory for <allocator>, size XXXXXXXXX, alignment=1B, flags 0x0, reason GLOBAL_ALLOCATION_LIMIT (early exit)
However GLOBAL_ALLOCATION_LIMIT is still much larger than sum of AB (Allocated bytes by allocators for heap and stacks) plus SHARED_MEMORY.
GLOBAL_ALLOCATION_LIMIT (GAL) = 3tb (3298534883328b), SHARED_MEMORY = 171.77mb (180117504b), CODE_SIZE = 2.34gb (2520866816b), OOM_RESERVATION_ALLOCATOR_SIZE = 96.14mb (100810752b)
PID=12345 (hdbindexserver), PAL=3tb (3298534883328b), AB=2tb (2199023255552b), UA=0, U=2tb (2199023255552b), FSL=0b, FMC=0b
Image /data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental.
SAP HANA Database >= 2.00.040
HANA, Fast Restart, Global Allocation Limit, Out of Memory, DRAM-NVM, FRO, signal 6, crash, secondary, error during log replay, Allocation failed, no.1000000, NVMLimitManager, Peak DRAM-NVM size , KBA , HAN-DB , SAP HANA Database , Problem
About this pageThis 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.