Db2 Instances Test

This test, executed by an internal agent, tracks various statistics at the instance level of a 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
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.

Measurements made by the test
Measurement	Description	Measurement Unit	Interpretation
Waiting agents:	Indicates the percentage of agents waiting to execute a unit of work.	Percent	It shows the percentage of agents that are waiting to execute (that is, that are asleep). Use this measure to adjust the MAXCAGENTS parameter setting for the database. If this value is high, you may consider increasing MAXCAGENTS.
Piped sorts accepted:	Indicates the percentage of piped sorts accepted during the interval.	Percent	Piped sorts reduce disk I/O and tend to be more efficient. A high percentage of piped sorts accepted indicate that efficient sorts are being performed. A low percentage indicates that sort heap and sort heap threshold may have to be adjusted. If this percentage is low, then increase SHEAPTHRES and possibly SORTHEAP.
Piped sort rejected:	Indicates the percentage of piped sort requests that were rejected.	Percent	Piped sorts reduce disk I/O and tend to be more efficient. A low percentage of piped sorts rejected indicate that efficient sorts are being performed. A high percentage of piped sorts rejected indicate that sort heap and sort heap threshold may have to be adjusted. If this percentage is high, then increase SHEAPTHRES and possibly SORTHEAP.
Agents registered:	Indicates the number of agents registered in the database manager instance that is being monitored (coordinator agents and subagents).	Number	This measure can be used to evaluate your setting for the MAXAGENTS configuration parameter.
Agents from empty pool:	Indicates how often an agent must be created because the pool is empty.	Percent	A high value may indicate that the NUM_POOLAGENTS configuration parameter should be increased. A low value suggests that NUM_POOLAGENTS is set too high, and that some of the agents in the pool are rarely used and are wasting system resources. A high percentage can also indicate that the overall workload for this node is too high. The workload can be adjusted by lowering the maximum number of coordinating agents specified by the MAXCAGENTS configuration parameter, or by redistributing data among the nodes.