SAP Knowledge Base Article - Preview

2682508 - DB6: How to check previous lock timeout or deadlock issue using DBA Cockpit


In your SAP system, the program or job ends with SQL0911N error. 

SQL0911N   The current transaction has been rolled back because of a deadlock or timeout.

Reason code 2 means:
The transaction was rolled back due to a deadlock.

Reason code 68 means:
The transaction was rolled back due to a lock timeout.

You want to check further for the reasons of the error using transaction DBA Cockpit.


1. The Data Collecotr Framework is set up correctly.
(Reference: DBA Cockpit guide => Configuration and Management of the System Landscape => Enablement of Databases for the Data Collection Framework)

2. Web Dynpro dbacockpit is enabled. (SAP Note 1245200)



SAP on IBM Db2 for Linux, UNIX, and Windows


SQL0911N, 2, 68, deadlock, lock timeout, dbacockpit , KBA , BC-DB-DB6-CCM , CCMS/Database Monitors , BC-DB-DB6-DBA , Database Administration , 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.