SAP Knowledge Base Article - Preview

3683129 - Savepoint lock failure and rapid growth of /hana/data and /hana/log leading to SAP HANA database unresponsiveness

Symptom

  • Filesystems /hana/data and /hana/log reached 100%, causing the SAP HANA database to become unresponsive.
  • Long-running transaction activities detected, resulting in a full-system dump.
  • In indexserve_<host>.<port>.<counter>.trc -  No space (rc= 28, 'No space left on device') ... path '/usr/sap/<sid>/HDB<inst>/<host>/trace/[DB_<database>]'
  • In indexserver_alert_<host>.trc: Transaction << <id> is now being exclusively used by thread = <thread_id> or/and  Could not acquire savepoint lock in xx microseconds.


Read more...

Environment

SAP HANA 2.0, Platform Edition

Product

SAP HANA, platform edition all versions

Keywords

savepoint lock failure, hana/data full, hana/log full, unresponsive database, long-running transaction, garbage collection, uncollected versions, fragmentation, data volume reclaim, SAP HANA database, savepoint issue, disk full error, rapid data growth, transaction blocking, LOBGarbageCollectorJob , 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.