Db2 Transactions Test

This test, executed by an internal agent, tracks various statistics pertaining to transactions in DB2 UDB database. The details of the test are provided below:

Target of the test : A DB2 database server

Agent deploying the test : An internal agent

Outputs of the test : One set of results for every database being monitored

Configurable parameters for the test
  1. TEST PERIOD – How often should the test be executed
  2. HostThe IP address of the DB2 server
  3. PortThe port number through which the DB2 server communicates. The default port is 50000.
Measurements made by the test:
Measurement Description Measurement Unit Interpretation

Commit rate:

Indicates the transaction throughput.  This measure is the sum of the committed statements attempted and internal commits (total number of commits initiated internally by the database manager.) per sec.


A decrease in this measure during the monitoring period may indicate that the applications are not doing frequent commits. This may lead to problems with logging and data concurrency.

The cause has to be probed in the application.


Rollback rate:

Indicates the rate of unit of work rollbacks.

Rollbacks /Sec

A high rollback rate is an indicator of bad performance, since work performed up to the rollback point is wasted. The cause of the rollbacks has to be probed in the application.

Transaction rate:

Indicates the rate of commits and rollbacks for the application using the DB2 Connect gateway.


A high transaction rate with high rollback rate indicates bad performance.


Since these measures pertain to the factors that are application dependent, no specific boundaries have been indicated for these values.