SAP Knowledge Base Article - Preview

1648566 - How to collect blocking lockstats history in DBACockpit


The database uses locks to control data integrity in concurrency situations. A blocking lock is a situation in which a session holds a lock on a resource and thereby causes another session to wait in a holding queue until the current process is entirely done with the resources. As soon as the first session is complete, the blocked session resumes operation. In a normal server environment, infrequent blocking locks are normal and acceptable - frequent blocking locks might indicate several kinds of problems.

SQL Server itself does not log information about the blocking lock situations which occur - once a blocking lock situation has resolved it leaves no information in the database that would allow further analysis. For hanging situations or performance analysis it is important to have the history of blocking locks.



SAP systems with transaction DBACockpit based on Microsoft SQL Server


history performance blocking lock history turn collector job on st04 dbacockpit , KBA , BC-DB-MSS-CCM , CCMS/Database Monitors for SQL Server , 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.