1984422 - How-To: Analyzing SAP HANA Out-of-memory (OOM) Dumps

The following SAP HANA alert is issued:

Alert 46: Runtime dump files

The SAP HANA database has generated out-of-memory (OOM) trace files in the trace directory (/usr/sap/<sid>/HDB<nr>/<nodehostname>/trace) using the following naming convention:

<processname>_<hostname>.<number>.rtedump.<number>.oom.trc

Example for an actual file name:

indexserver_saphana1.39503.rtedump.72290.oom.trc

You experience memory shortages and you have generated a runtime dump as described in SAP Note 1813020.

In HANA DB Studio, on the Diagnosis Files tab, you find trace files when entering the filter string 'oom' or 'rtedump' and sort by the Modified column.

Files with a name containing 'composite_oom' are linked to the statement memory limit. See SAP Note 1999997 ("Is it possible to limit the memory that can be allocated by a single SQL statement?") for more details. These files don't indicate overall OOM situations but a high statement-specific memory consumption. This scenario is not discussed in detail in this SAP Note. Normally the analysis is quite straight-forward because it is already clear which activity ran into the memory limit.

"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

Failed to allocate
MEMORY_OOM
allocators
inclusive_size_in_use
exclusive_size_in_use
M_CONTEXT_MEMORY
pool
statement_memory_limit , KBA , HAN-DB-ENG , SAP HANA DB Engines , HAN-DB , SAP HANA Database , How To