Db2 Transaction Test

This test tracks various statistics pertaining to the transactions executing on a DB2 database.

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 on the DB2 database server that is currently active

Configurable parameters for the test
  1. TEST PERIOD – How often should the test be executed
  2. Host – The IP address of the DB2 server
  3. Port – The port number through which the DB2 server communicates. The default port is 50000.
  4. user - Specify the name of the user who has any of the following privileges to the specified DATABASE: SYSADM or SYSCTRL or SYSMAINT or SYSMON. You can create a separate user on the OS hosting the DB2 server for this purpose, and assign any of the aforesaid privileges to that user. The steps for the same are detailed in the Creating a Special User for Monitoring DB2.
  5. password - Enter the password of the specified USER in the PASSWORD text box.
  6. confirm password – Confirm the password by retyping it here.
  7. database - Specify the name of the database on the monitored DB2 server to be used by this test
  8. SSL- If the target database server is SSL-enabled, then set the SSL flag to Yes. If not, then set the SSL flag to No.
  9. Trust Store file name- The trust store file contains certificates from trusted Certificate Authorities (CAs). These certificates are used by eG agent to verify the authenticity of servers hosting DB2 UDB and establish a secure connection with the server using SSL. Specify the filename for Trust store file in Trust Store file name text box.
  10. Trust Store Password- The trust store password is the passphrase or key used to encrypt and decrypt the trust store file. This password is required by the eG Agent when it needs to access the trust store file to establish secure connections. Specify the password in Trust Store password text box.
  11. Confirm Password- Confirm the Password by retyping it in the Confirm Password text box.
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 second.

Commits/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.

Trans/Sec

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