eG Monitoring
 

Measures reported by SybLockStatsTest

A Sybase server provides data concurrency and integrity between transactions using locking mechanisms. The locking activity of a database server must 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. The SybLockStatsTest monitors the locking activity on a database server instance. The measures made by this test are as follows:

Measurement Description Measurement Unit Interpretation
Num_of_Locks Gives the total number of locks that are held. Number

A high value may indicate one of the following:

  • Too many transactions happening
  • Locked resources not being released properly
  • Locks are being held unnecessarily.
Average_block_time Indicates the average time for which a process is blocked Secs A high value may indicate one of the following:
  • Locked resources not being released properly
  • Locks are being held unnecessarily

The detailed diagnosis of the Avg_block_time measure, if enabled, provides the complete information (i.e. duration for which the lock was held, the object that was locked, the type of lock held, etc.) pertaining to the locks that are being held currently.