SAP Knowledge Base Article - Preview

1977276 - How to handle HANA Alert 48: 'Check a long-running uncommitted write transaction'


  • You receive HANA Alert 'Uncommitted Write Transaction' (Alert ID 48).
  • The corresponding Alert text (as displayed in HANA Studio) is:
    'Uncommitted write transaction running for n minutes found. Transaction ID: <id>. Client PID: <pid>.'
  • These alerts are also recorded in the alert trace of the indexserver (indexserver_alert_<host>.trc), for eg:

long running uncommitted write transaction detected: CONNECTION ID = 200647, HOST = <dbhost>:30003, CLIENT HOST = <clienthost>, CLIENT PID = 11567, TRANSACTION_ID = "902", TRANSACTION TOTAL EXECUTED TIME = 6321 sec
The long running uncommitted write transaction possibly incurs performance degradation of HANA database. Please commit/rollback a transaction in application or kill the connection by "ALTER SYSTEM DISCONNECT SESSION '200647' "



SAP HANA Database


SAP HANA, platform edition all versions


Indexserver alert, DBACOCKPIT;  m_connections;  m_service_threads; call stacks; threads; , KBA , HAN-DB-MON , SAP HANA Monitoring , SV-PERF , Performance Problems , HAN-DB-PERF , SAP HANA Database Performance , How To

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.