Sperrstatistik anzeigen

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 2007/04/30 09:53:50

Row in the Statistics Table		Meaning
`Enqueue Operations`	`1826687`	Number of lock requests
`Rejected`	`37976`	Rejected lock requests
`Errors Occurred`	`0`	Error
`Dequeue operations`	`1327514`	Release requests (DEQUEUE)
`Errors Occurred`	`0`	Release (dequeue) errors
`Dequeue-All Operations`	`905744`	Release of all locks for a LUW
`Cleanup operations`	`38`	Release of all locks in a server (when server is shut down)
`Backup Operations`	`423`	Number of requests passed to the update process
`Read Operations`	`32325`	Requests to read lock entries (for example, SM12)
`Compress operations`	`0`	Internal use
`Verify operations`	`0`	Internal use
`Records written`	`15822`	Write accesses to file
`to the backup file`	`1260`	Write accesses to backup file
`Maximum Number of Lock Owners`	`14562`	Maximum number of owner names that can be stored in the lock table
`Maximum Fill Level`	`30`	Maximum number of owners stored simultaneously in the lock table
`Current Fill Level`	`8`	Current number of owners in the lock table
`Maximum Number of Lock Arguments`	`14562`	Analog: Occupancy of the lock table, elementary locks - affecting arguments
`Maximum Fill Level`	`305`
`Current Fill Level`	`23`
`Maximum Number of Lock Entries`	`14562`	Analog: Occupancy of the lock table, elementary locks - affecting names
`Maximum Fill Level`	`305`
`Current Fill Level`	`23`
`Update, Fill Level at Maximum`	`3`	Maximum number of accumulated update requests
`Current Fill Level`	`0`	Number of outstanding update requests
`Time in Lock Table / Seconds`	`133.713869s`	Total time required for lock operations
`Wait for Lock Table / Seconds`	`0.623998s`	Total wait time of all work processes for accessing lock table
`Time in Lock Server /Seconds`	`352.896785s`	Total time needed for lock operations by all processes in the enqueue server

Note Note

The occupancy of the lock table is important for monitoring the lock mechanism. This should never overflow. An overflow is pending if the maximum fill level for lock owners, lock arguments, or lock entries is equal to or close to the respective maximum number.

End of the note.