/support/notes/service/sap_logo.png){kind=logo}
SAP Knowledge Base Article - PreviewSymptom
How to proactively monitor long running blocking sessions and lock wait events in an SAP system running on IBM Db2. This article describes the available tools and methods for identifying and analysing lock contention in the DB2 LUW database.
Read more...
Environment
Db2 LUW IBM
Product
Keywords
SAP on Db2, IBM Db2 LUW, Db2 11.5, Db2 12.1, lock monitoring, lock wait, lock waits, lock timeout, deadlock, locking, DBACOCKPIT, DBA Cockpit, Lock-Wait Events, Lock Event Monitor, db6util, db6util --sl, db6util --sd, db2pd, MON_GET_APPL_LOCKWAIT, MON_GET_APPL_LOCKWAIT table function, db2diag.log, DBSL deadlock trace, SYSLOG, developer trace, application handle, lock object, lock mode, SQL monitoring, lock diagnostics, performance troubleshooting, database contention, SAP Basis, SAP DBA, Db2 monitoring, wait chain, lock analysis, concurrency, blocking session, blocked application. , KBA , BC-DB-DB6 , DB2 Universal Database for Unix / NT , 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.
/support/notes/service/twitter.svg)
/support/notes/service/youtube.svg)
/support/notes/service/linkedin.svg)
/support/notes/service/instagram2.svg)