Skip to end of metadata
Go to start of metadata


This page is to provide you with resources to refer to for analyzing out of memory (OOM) dumps.

The KBA 1984422   - SAP HANA: Analysis of Out-of-memory (OOM) Dumps, gives you symptom, cause, and resolution for OOM dumps. In the resolution session of the KBA, it provides useful instructions on how to troubleshoot the OOM dump. The tool hdbcons provides expert functionality to analyze memory issues. For more information see SAP note 1786918  - Required information to investigate high memory consumption

As a side note, by default OOM dump is written once in 24 hours. What that means is if multiple OOM errors happen only the first occurrence of the OOM error will generate an OOM dump, and the rest will be recorded in the service trace.  If you need multiple OOM dump for analysis, you may modify the parameter oom_dump_time_delta (seconds) by running the alter system alter configuration command. The following command will set the interval to 10 minutes.

-          ALTER SYSTEM ALTER CONFIGURATION ('global.ini', 'SYSTEM') SET ('memorymanager', 'oom_dump_time_delta') = '600' with reconfigure;

To deactivate:

-          ALTER SYSTEM ALTER CONFIGURATION ('global.ini', 'SYSTEM') UNSET ('memorymanager', 'oom_dump_time_delta') with reconfigure;

Related Documents

 Troubleshooting guide:

SAP HANA Memory Usage Explained:

Related Videos:

SAP HANA Academy - SAP HANA Support: Out of Memory Dump Analysis:


Related SAP Notes/KBAs

SAP Guided Answer:  How to troubleshoot HANA High Memory Consumption

SAP Note: 1984422 - SAP HANA: Analysis of Out-of-memory (OOM) Dumps

SAP Note: 1786918 - Required information to investigate high memory consumption

 SAP Note: 1999997 - FAQ: SAP HANA Memory

SAP Note: 1998599 - SAP HANA: High Memory Consumption due to Translation Tables

SAP Note: 1840954 - Alerts related to HANA memory consumption

SAP Note 1813020 - How to generate a runtime dump on SAP HANA

SAP Note 1813245 - SAP HANA DB: Row store reorganization



  • No labels