SAP Knowledge Base Article - Preview

3695616 - HANA killed by os oom-kill while HANA memory usage is below global allocation limit.

Symptom

  • Indexserver crashing without a crash dump.
  • /var/log/messages file contains traces similar to:

    2025-08-25T10:30:02.327157+00:00 <hostname> kernel: [13630.495916][    T1] Out of memory: Killed process 20023 (hdbindexserver) total-vm:108844012kB, anon-rss:67466664kB, file-rss:0kB, shmem-rss:36429764kB, UID:1005 pgtables:207352kB oom_score_adj:0

    2025-08-25T10:54:30.703208+00:00 <hostname> kernel: [15098.873498][    T1] Out of memory: Killed process 5798 (hdbindexserver) total-vm:108119776kB, anon-rss:66974992kB, file-rss:0kB, shmem-rss:36317224kB, UID:1005 pgtables:206524kB oom_score_adj:0

  • Indexserver process killed by OS OOM-KILL.
  • HANA memory utilization below Global allocation limit and no out of memory dump generated by HANA.


Read more...

Environment

SAP HANA Database

Product

SAP HANA 1.0, platform edition ; SAP HANA, platform edition 2.0 ; SAP S/4HANA 2023

Keywords

memory allocation issue, global allocation limit, SAP HANA, OS OOM-KILL, out of memory , KBA , 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.