DB2 DPF Connection Statistics Test

DB2 DPF Connection Statistics track client connections across database partitions. They include metrics like **active connections**, **idle connections**, **failed attempts**, and **connection time**. These stats help monitor workload distribution, detect bottlenecks, and optimize performance in a multi-partitioned DB2 environment. Use `db2pd -conn` for real-time insights.

Monitoring DB2 DPF Connection Statistics helps ensure optimal performance, detect connection bottlenecks, and balance workloads across partitions. It aids in identifying idle or failed connections, supports capacity planning, and enhances troubleshooting. Regular monitoring ensures high availability and efficient resource utilization in distributed database environments.

This test monitors the connection statistics and reports key metrics like total connections, canceled connections, idle connections etc. These metrics provide actionable insights to administrators about the maintenance of database server.

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

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.
DD Row Count	By default, the detailed diagnosis of this test, if enabled, will report only the top-10 records. This is why, the DD Row Count parameter is set to 10 by default. If you want to include more or less records in detailed diagnosis, then change the value of this parameter accordingly.
Detailed Diagnosis	To make diagnosis more efficient and accurate, the eG Enterprise embeds an optional detailed diagnostic capability. With this capability, the eG agents can be configured to run detailed, more elaborate tests as and when specific problems are detected. To enable the detailed diagnosis capability of this test for a particular server, choose the On option. To disable the capability, click on the Off option. The option to selectively enable/disable the detailed diagnosis capability will be available only if the following conditions are fulfilled: The eG manager license should allow the detailed diagnosis capability Both the normal and abnormal frequencies configured for the detailed diagnosis measures should not be 0.

Measurements made by the test
Measurement	Description	Measurement Unit	Interpretation
Total connections	Indicated the total number of connections to the database server.	Number	Total number of connection should be optimal, if the number is increasing or decreasing very fast it should be investigated.
Cancelled connections	Indicates the number of connections to the server which have been cancelled.	Number	If the connections are reportedly getting cancelled it should be investigated.
Executing connections	Indicates the number of connections to the server which are currently executing.	Number	This number should ideally be high.
Idle connections	Indicates the number of connections to the server which are currently idle.	Number	The number should not be too high because rather than being idle for long time the connections should be recycled.
Initialized connection	Indicates the number of connections to the server which have just been initialized.	Number
Queued connections	Indicates the number of connections to the server which are still queued.	Number
Terminated connections	Indicates the number of connections to the server which have been terminated.	Number	If the connections are repeatedly getting terminated it should be investigated.