SAP Knowledge Base Article - Preview

3195270 - What high Heap memory fragmentation can indicate

Symptom

You are facing with out of memory situation and in the indexserver OOM trace file you can see the following:

At the section of: 

[MEMORY_OOM]  Information about current out of memory situation: (2022-04-22 03:13:10 882 Local)
OUT OF MEMORY occurred.
Host: zisasshdeddb7
Executable: hdbindexserver
PID: 25678
Failed to allocate 1mb (1062241b).

Allocation failure type: GLOBAL_ALLOCATION_LIMIT

When you are checking the heap allocators and the sump up section of the total allocated memory, you can see the following at the Heap memory Fragmentation:

Total allocated memory= 251.79gb (268215382016b)
Total used memory     = 206.77gb (219879469313b)
Sum AB                = 269458013943
Sum Used              = 210011101348
Heap memory fragmentation: 19% (this value may be high if defragmentation does not help solving the current memory request)


Read more...

Environment

SAP HANA, platform edition

Product

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

Keywords

Out Of Memory, OOM, Heap memory fragmentation , KBA , HAN-DB-ENG , SAP HANA DB Engines , How To

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.