Sybase Lock Stats Test

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 SybaseLockStats test monitors the locking activity on a database server instance.

Target of the test : A Sybase ASE (Below v15) server

Agent deploying the test : An internal agent

Outputs of the test : One set of results for every Sybase instance monitored.

Configurable parameters for the test
Parameter Description

Test Period

How often should the test be executed.


Refers to the IP address of the Sybase server.


The port number at which the Sybase server listens to.


A Sybase user who has the “sa_role”.


The password corresponding to the above user.

Confirm Password

Confirm the password by retyping it here.

Detailed Diagnosis



  • The eG manager license should allow the detailed diagnosis capability
Measurements made by the test
Measurement Description Measurement Unit Interpretation


Gives the total number of locks that are held.


A high value may indicate one of the following:

  1. Too many transactions happening
  2. Locked resources not being released properly
  3. Locks are being held unnecessarily.

Avg block time due to locks

Indicates the average time for which a process is blocked


A high value may indicate one of the following:

  1. Locked resources not being released properly
  2. Locks are being held unnecessarily.

The detailed diagnosis of this 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.