Messages are stored in a database. The distribution of users on disks, the size of their mailbox, and disk requirements affect the store performance. These are described in the following subsections:
The state of database-locks is held by different server processes. These database locks can affect the performance of the message store. 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. There are legitimate reasons for a queue to back up, so it is useful to have a history of the queue length in order to diagnose problems.
Number of transactions are accumulating and not resolving.
Use the command counterutil -o db_lock
Database log files refer to sleepycat transaction checkpointing log files (msg_svr_base/store/mboxlist). Log file build up is a symptom of database checkpointing not happening. Log file build up can also be due to stored problems.
There should be 2 or 3 log files. If there are more, it is a sign of a potentially serious problem. The message store uses a few databases for messages and quotas, and a problem with those can lead to problems for all of the mail server.
Look in the msg_svr_base/store/mboxlist directory and make sure there are only 2 or 3 files.