Db2 Connections Test
The Db2 Connections test reports key statistics pertaining to the local and remote connections to the DB2 database manager.
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 DB2 database server being monitored
| Parameter | Description |
|---|---|
|
Test period |
How often should the test be executed |
|
Host |
The IP address of the DB2 server |
|
Port |
|
|
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 |
|
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. |
|
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 UDB 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 UDB 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. |
| Measurement | Description | Measurement Unit | Interpretation |
|---|---|---|---|
|
Total connections: |
Indicates the total number of local and remote connections that are currently present in the database manager. |
Number |
|
|
Local connections: |
Indicates the number of local applications that are currently connected to a database within the database manager instance being monitored. |
Number |
This number can help you determine the level of concurrent processing occurring in the database manager. This number only includes applications that were initiated from the same instance as the database manager. The applications are connected, but may or may not be executing a unit of work in the database. When used in conjunction with the Remote connections measurement, this measure can help you adjust the setting of the MAXAGENTS configuration parameter. |
|
Remote connections: |
Indicates the percentage of agents waiting for a token so they can execute a transaction in the database manager. |
Percent |
This number does not include applications that were initiated from the same instance as the database manager. When used in conjunction with the Local connections measure, this measure can help you adjust the setting of the MAX_COORDAGENTS configuration parameter. |
|
Local connections in exec: |
Indicates the number of local applications that are currently connected to a database within the database manager instance being monitored and are currently processing a unit of work. |
Number |
This number can help you determine the level of concurrent processing occurring in the database manager. This number only includes applications that were initiated from the same instance as the database manager. When used in conjunction with the Remote connections in exec measure, this measure can help you adjust the setting of the MAXCAGENTS configuration parameter. |
|
Remote connections in exec: |
Indicates the number of remote applications that are currently connected to a database and are currently processing a unit of work within the database manager instance being monitored. |
Number |
This number can help you determine the level of concurrent processing occurring on the database manager. This number does not include applications that were initiated from the same instance as the database manager. When used in conjunction with the Local connections in exec measure, this metric can help you adjust the setting of the MAXCAGENTS configuration parameter. |
Note - This test will no longer be supported from DB2 10.5 version.