- You observe a hanging situation or an unresponsive state on your HANA database.
Further investigation reveals blocked savepoints because another transaction(s) was withholding the ConsistentChangeLock from the savepoint operation, thus blocking any other transactions from making changes on the underlying table. In the 'waitForLock' phase the savepoint has to wait for an exclusive access to the ConsistentChangeLock.
If another database operation holds this lock for a longer time, delays are possible.
- Within the diagnosis files section, there are one or more runtime dump traces which capture these events under the following trace file name: '<service>_<host>.<port>.rtedump.<timestamp>.savepoint_blocked.trc'
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 PLATFORM EDITION 1.0
- SAP HANA PLATFORM EDITION 2.0
Savepoint blocked, long running savepoint, system slow, system hang, system unresponsive, system standstill, savepoint_blocked, Duration of Blocking Savepoint Phase, Savepoint block, Savepoint Critical Blocking Phases, Savepoint issues, Savepoint pending, High duration of blocking savepoint phases , KBA , HAN-DB-PER , SAP HANA Database Persistence , HAN-DB-PERF , SAP HANA Database Performance , Problem
About this pageThis 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.