SAP Knowledge Base Article - Preview

3698464 - Hana database does not start after data volume full.

Symptom

  • SAP HANA database fails to start after the /hana/data volume becomes full.
  • Error messages indicate long-running node starting statuses detected, with global runtime dumps created.
    [1115418]{-1}[-1/-1] 2025-12-21 19:15:43.510609 e KernelSentinel   KernelSentinelJob.cpp(02127) : Long running node(2) starting status detected. Global runtime dump created. duration(s): 660, timeout(s): 600
    [1115418]{-1}[-1/-1] 2025-12-21 19:15:43.510670 e KernelSentinel   KernelSentinelJob.cpp(02127) : Long running node(3) starting status detected. Global runtime dump created. duration(s): 660, timeout(s): 600
    [1115418]{-1}[-1/-1] 2025-12-21 19:15:43.510673 e KernelSentinel   KernelSentinelJob.cpp(02127) : Long running node(4) starting status detected. Global runtime dump created. duration(s): 660, timeout(s): 600


Read more...

Environment

  • SAP HANA 2.0 

Product

SAP HANA, platform edition 2.0

Keywords

hana database, data volume full, log volume full, log_disk_usage_limit, log segment creation failure, runtime dump, scriptserver, /hana/log, /hana/data, database startup failure, SAP HANA , KBA , HAN-DB-ENG , SAP HANA DB Engines , 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.