IMS Store Locks Test

The Oracle Communications messaging server instance message store contains a database (Berkley DB) that stores information about the mailboxes on the server and stores quota information about the mailboxes. The state of DB-locks is held by different server processes. These database locks can affect the performance of the message store. This test monitors the behaviour of the database locks.

Target of the test : An Oracle Communications Messaging Server

Agent deploying the test : An internal agent

Outputs of the test : One set of results for every Oracle Communications messaging server.

Configurable parameters for the test
Parameter Description

Test period

How often should the test be executed.


The host for which the test is to be configured.


The SMTP port of the Oracle Communications messaging server.


Specify the path to the directory into which all servers of a given server group (i.e., all servers managed by a given Administration Server) are installed. For example, in Windows environments, the path can be expressed as: C:\iOracom\server5. In Unix platforms, the path can be specified in the following format: /usr/iOracom/server5. A server group may include other Oracle Communications messaging servers in addition to the messaging server.


Enter the full path to the counter registry to use. By default, the path to the counter registry will be: <IPLANET_MESSAGING_SERVER_ROOT_DIR>/<SERVER_INSTANCE>/counter/counter. Here, SERVER_ROOT_DIR will be the value of the ServerRoot parameter above, and the SERVER_INSTANCE is the name of the instance of the messaging server specified during installation. For example, in Windows environments, the path specification can be: C:\iPlanet\Server5\msg-egtes\counter\counter, and in Unix environments, it can be: usr/iplanet/server5/msg-sun08/counter/counter.

Measurements made by the test
Measurement Description Measurement Unit Interpretation

Lock requests

Indicates the rate of database lock requests.



Lock releases

Indicates the rate of database lock releases.



Deadlocks occurred

The rate of deadlocks


A non zero value for this measure is indicative of the occurrence of a deadlock in the message store database. In case of deadlocks, messages will not be getting inserted into the store at reasonable speeds and the ims-ms channel queue will grow larger as a result. The stored utility will automatically perform Deadlock detection and rollback of deadlocked database transactions.