Db2 Activity Test

This test measures the level of SQL activity on the DB2 database server, and reveals how well the server processes SQL queries.

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. HostThe IP address of the DB2 server
  3. PortThe 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
Measures made by the test:
Measurement Description Measurement Unit Interpretation

Dynamic SQL Rate:

Indicates the rate of dynamic SQL statements that were attempted.

Stmts/Sec

This is an indication of throughput of the system during the monitoring period. A high value of dynamic SQLs and low value of failed SQLs indicate good throughput.

Select SQL Rate:

Indicates the rate at which SELECT SQL statements were executed during the last measurement period.

Stmts/Sec

This measure can be used to determine the level of database activity.

UID SQL Rate:

Indicates the rate at which update/delete/insert statements were issued during the last measurement period.

Stmts/Sec

This measure can be used to determine the level of database activity.

Failed SQL Rate:

Indicates the rate at which SQL statements failed.

Stmts/Sec

A relatively high value indicates a problem. Failed SQL statements waste system resources. Hence, the value of this measure should be very low.

Percent Failed SQL:

Indicates the percentage of SQL statements that failed during the interval. This value includes all SQL statements that received a negative SQLCODE

Percent

Percent DDL SQL:

Denotes the percentage of SQL statements that were DDL(Data Definition Language) during the last measurement period.

Percent

This value should normally be low.

Percent UID SQL:

Indicates the percentage of update/insert/delete statements executed during the last measurement period.

Percent

This measure can be used to determine the level of database activity.