eG Help

A Progress database server provides data concurrency and integrity between transactions using locking mechanisms. The locking activity of a database server should be monitored carefully because an application holding a specific lock for a long time could cause a number of other transactions relying on the same lock to fail.

This test indicates the level of locking activity on a database in terms of the number of locks of different modes held by each user and the time taken by each user to hold a RECORD lock and TRANSACTION lock.

Output of the test : One set of results for every user accessing the locks on the target Progress database server being monitored.

Measurement	Description	Measurement Unit	Interpretation
Exclusive_locks	Indicates the rate at which EXCLUSIVE locks were held by this user on the database during the last measurement period.	Locks/sec	Exclusive locks are used to lock data being modified by one transaction thus preventing modifications by other concurrent transactions. You can read data held by exclusive lock only by specifying a NOLOCK hint or using a read uncommitted isolation level. Because DML statements first need to read the data they want to modify you’ll always find Exclusive locks accompanied by shared locks on that same data.
Record_locks	Indicates the rate at which RECORD locks were held by this user on the database during the last measurement period.	Locks/sec
Record_lock_waits	Indicates the rate at which this user had to wait to hold the RECORD locks on the database during the last measurement period.	Waits/sec
Shared_lock	Indicates the rate at which SHARED locks were held by this user on the database during the last measurement period.	Locks/Sec
Transaction_lock	Indicates the rate at which TRANSACTION locks were held by this user on the database during the last measurement period.	Locks/sec
Transaction_lock_waits	Indicates the rate at which this user had to wait to hold the TRANSACTION locks on the database during the last measurement period.	Waits/Sec