Informix Locks Test

This test reports the lock related measures of an Informix database server.

Target of the test : An Informix Dynamic server

Agent deploying the test : An internal agent

Outputs of the test : One set of results for the Informix server being monitored.

Configurable parameters for the test
Parameters Description

Test Period

This indicates how often should the test be executed.


The IP address of the Informix Dynamic server.


The port number at which the specified host listens to.


The Informix server instance being monitored.


Specify the name of a database on the server.


A valid Informix user name to login to the specified database.


The password corresponding to the above user.

Confirm Password

Confirm the Password by retyping it here.


Specify the language/locale in which your database is installed. This will allow you to return the query in the language supported by your database. By default this attribute is set to “none”, which means that by default, queries are returned in the English locale.


Specify the language/locale in which the eG agent is running. Normally, when you use an internal agent to monitor Informix, the ClientLocale and DBLocale will be same. However, the ClientLocale may differ when you are monitoring the Informix tests using a remote agent (agentless monitoring). By default, the ClientLocale is set to “none”, indicating that the eG agent runs in the English locale, by default.

Detailed Diagnosis

To make diagnosis more efficient and accurate, the eG Enterprise embeds an optional detailed diagnostic capability. With this capability, the eG agents can be configured to run detailed, more elaborate tests as and when specific problems are detected. To enable the detailed diagnosis capability of this test for a particular server, choose the On option. To disable the capability, click on the Off option.

The option to selectively enable/disable the detailed diagnosis capability will be available only if the following conditions are fulfilled:

  • The eG manager license should allow the detailed diagnosis capability
  • Both the normal and abnormal frequencies configured for the detailed diagnosis measures should not be 0.
Measurements made by the test
Measurement Description Measurement Unit Interpretation

Lock requests

The number of lock requests received.


A high value indicates that there is high locking activity in the system and may need close scrutiny for the type of locks being requested. The detailed diagnosis of this measure, if enabled, provides a list of top 10 user sessions holding maximum number of locks.

Lock waits

The number of lock waits.


A high value of waits can have an adverse impact on application performance. Possible reasons for this behavior could be:

  • Inadequate number of locks available in the database
  • Unusually high locking behavior of applications accessing the database
  • Improper database application design, etc.

Lock timeouts

The number of locks that timed out.


Lock timeouts can be useful for removing tasks that acquire some locks, and then wait for long periods of time blocking other users.


The number of deadlocks.


A deadlock may arise due to various situations including bad design of queries and deficient coding practices. A deadlock is a situation where both/all the lock requestors are in a mutual or a multi-way tie. Any deadlocks are detrimental to database application performance. The detailed diagnosis of this measure, if enabled, will report the details of user sessions performing deadlocks.