Displaying Lock Statistics (SAP Library - The SAP Lock Concept (BC-CST-EQ))

Displaying Lock Statistics

Use

You can use lock statistics to monitor the locks that are set in your system. This can be useful for rectifying configuration problems.

Prerequisites

You do not need to log onto the application server on which the lock server is running; the global statistics are always displayed.

Procedure

In the initial lock management screen, choose ( sm12 ) Extras ® Statistics to display the statistics. These are the statistics that have been compiled since the last time the lock server was restarted.

Result

The information provided by the enqueue statistics is explained in the table below.

Enqueue Statistics at 1999/02/16 09:53:50

Enqueue Requests.....: 110914	Number of lock requests
Rejects...........: 217	Rejected lock requests
Errors............: 0	Errors
Dequeue Requests.....: 29149	Release requests ( DEQUEUE )
Errors............: 0	Release (dequeue) errors
DequeueAll Requests..: 224832	Release of all locks for a LUW
CleanUp Requests.....: 217
Backup Requests......: 732
Reporting Requests...: 66
Compress Requests....: 0
Verify Requests......: 0
Writes to File.......: 12548	Write accesses to file
Backup............: 7091
Owner Names..........: 5457	Maximum number of owner names that can be stored in the lock table
Peak Util.........: 5	Maximum number of owners stored simultaneously in the lock table
Actual Util.......: 0	Current number of owners in the lock table
Granule Arguments....: 5457	Similar: occupancy of the lock table, elementary locks - affecting arguments
Peak Util.........: 65
Actual Util.......: 0
Granule Entries......: 5457	Similar: occupancy of the lock table, elementary locks - affecting names
Peak Util.........: 65
Actual Util.......: 0
Update Queue Peak....: 2
Actual ...........: 0
Total Lock Time......: 2407.752370s total	Total time required for lock operations
Total Lock Wait Time.: 1066.962126s total	Total wait time

Note

The occupancy of the lock table is important for monitoring the lock mechanism. This should never overflow. An overflow is pending if the Peak Util for Owner Names, Granule Arguments, or Granule Entries is equal to or has nearly reached the maximum value.