Db2 DPF Transactions Test

This test tracks various statistics pertaining to the transactions executing on each logical partition of a DB2 database.

Target of the test : A DB2 DPF server

Agent deploying the test : An internal agent

Outputs of the test : One set of results for every logical partition of each database on the DB2 database server that is currently active

Configurable parameters for the test
Parameter Description

Test period

How often should the test be executed

Host

The IP address of the DB2 server

Port
  • The port number through which the DB2 server communicates. The default port is 50000.
    		•

    User

    Specify the name of the user who is authorized to access the target database server and collect the required metrics in this text box. You can create a separate user on the OS hosting the DB2 server for this purpose. The steps for the same are detailed in the Creating a Special User for Monitoring DB2 Server topic.

    Password

    Enter the password of the specified USER in the PASSWORD text box.

    Confirm Password

    Confirm the Password by retyping it in the Confirm Password text box.

    Database

    Specify the name of the database on the monitored DB2 server to be used by this test.

    Include DB

    Specify a comma-separated list of databases that you wish to monitor in the Include DB text box.

    Exclude DB

    Specify a comma-separated list of databases that need to be excluded from monitoring in the Exclude DB text box.

    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.

    Trust Store File Name

    This parameter is applicable only if the target DB2 database is SSL-enabled, if not, set this parameter to none. Specify the file name of the client-side SSL truststore that contains the server certificate required for establishing an SSL connection. The truststore is used to verify the identity of the server and enable a secure communication channel.

    By default, the truststore file should be placed in:<EG_INSTALL_DIR>/jre/lib/security/mytruststore.jks

    Here, mytruststore.jks is the Truststore file name. You may change this to any valid file name. By default, none is specified against this text box.

    Trust Store Password

    This parameter is applicable only if the target DB2 database is SSL-enabled, if not, set this parameter to none. If a Truststore File name is provided, then, in this text box, provide the password that is used to obtain the associated certificate details from the Truststore File. By default, this parameter is set to none.

    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 on this logical partition 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.

    Transactions/Sec

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

    Application commit rate

    Indicates the number of committed transactions executed by the application per second through the DB2 Connect gateway.

    Commits/Sec

    A low application commit rate may suggest that the application is not performing frequent commits, which could affect concurrency and logging efficiency. The application logic should be examined to confirm the cause.

    Application rollback rate

    Indicates the number of transaction rollbacks performed by the application per second.

    Rollbacks/Sec

    A high rollback rate reflects wasted processing effort and may be an indicator of application or transaction design issues. The reasons for frequent rollbacks must be investigated at the application level.

    Application transaction rate

    Indicates the overall rate of transactions (both commits and rollbacks) executed by the application through the DB2 Connect gateway.

    Transactions/Sec

    A high transaction rate combined with a high rollback rate signals inefficient or faulty application behavior. A balanced transaction rate with fewer rollbacks indicates healthy performance.