SAP Knowledge Base Article - Preview

2964136 - Heap memory fragmentation


  • SQL: "HANA_Memory_TopConsumers_TimeSlices" (SAP Note 1969700) gives high value for item "Heap (Fragmentation)".

    1 ;2020/08/28 10:00:00;Space used (GB); 100;Heap (Fragmentation); 25; 25;
    2 ;2020/08/28 09:00:00;Space used (GB); 100;Heap (Fragmentation); 25; 25;
    3 ;2020/08/28 08:00:00;Space used (GB); 100;Heap (Fragmentation); 25; 25;

  • SQL: "HANA_Memory_ProcessMemory" (SAP Note 1969700) gives high value for column "FRAG_GB".

    |saphana|30003| 176.55| 176.14| 155.34| 0.00| 20.80| 99.77| 87.98| 0.00| 11.78|

  • HANA DB trace show high value for "Heap memory fragmentation"

    Failed to allocate 2565818396904 byte. ... Heap memory fragmentation: 58% (this value may be high if defragmentation does not help solving the current memory request)

Image /data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental.



  • HANA database platform 1.0
  • HANA database platform 2.0


SAP HANA, platform edition all versions


OOM, dump, run time, rtedump, Failed to allocate, mm poolallocator , KBA , HAN-DB-PERF , SAP HANA Database Performance , 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.