DB2 Purescale SQL Network Test

In DB2 pureScale, the SQL network refers to the communication infrastructure that enables SQL requests and responses to flow between:

Client applications, DB2 pureScale members and indirectly, the Cluster Caching Facility (CF).

Monitoring SQL Network in pure Scale is important so that administrator can have a check on below points-

Performance: Efficient networking ensures fast query execution and low latency.

Scalability: Supports adding more members without degrading performance.

Availability: Enables failover and rerouting in case of member failure.

Consistency: Ensures all members have a synchronized view of the data.

This test monitors DB2 pureScale Members and reports the metrics like - Database connection availability, Cluster availability, Query processor availability, and Records fetched etc.

Target of the test : A DB2 Purescale database cluster.

Agent deploying the test : An internal agent

Outputs of the test : One set of results for the target DB2 Purescale cluster being monitored

Configurable parameters for the test
Parameter	Description
Test Period	How often should the test be executed.
Host	Specify the IP address of the DB2 server in this text box.
Port	Specify the port at which the target host is listening. The default port is 50000.
Username, Password	To monitor Db2 UDB database server, the eG agent should be configured with the credentials of a user with any of the following privileges SYSADM or SYSCTRL or SYSMAINT or SYSMON. Specify the credentials of such a user in the User and Password text boxes. Confirm the Password by retyping it in the Confirm Password text box.
Database	The test uses a database on the monitored Db2 Purescale. Specify the name of the database in the Database text box.
SSL	If the target database server monitored is SSL-enabled, then set the SSL flag to Yes. If not, then set the SSL flag to No.
Include Available Nodes	In the Include Available Nodes text box, provide a comma-separated list of all the available nodes to be included for monitoring. This way, the test monitor and collect metrics from all the available nodes in the cluster. By default, this parameter is set to none. The format of this configuration is: HOSTNAME:PORT, for example, 172.16.8.136:3306,172.16.8.139:3306
Confirm Password	Confirm the Password by retyping it in the Confirm Password text box.
Query
DD Frequency	Refers to the frequency with which detailed diagnosis measures are to be generated for this test. The default is 1:1. This indicates that, by default, detailed measures will be generated every time this test runs, and also every time the test detects a problem. You can modify this frequency, if you so desire. Also, if you intend to disable the detailed diagnosis capability for this test, you can do so by specifying none against DD frequency.
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
Database connection availability	Indicates the number of database connections available out of total connections.	%	Ideally the availability should be near 100%, but look out for the trend, if it goes downward you need to act.
Database connection response time	Indicates the time in seconds it takes for database connection to respond.	Seconds	Again need to look into the trend of connection response time, it should not be increasing beyond an optimal value.
Cluster availability	Indicates the percentage availability of cluster.	%
Average response time	Indicates the average response time of the database connection.	Seconds
Query processor availability	Indicates the percentage availability of query processor..	%	Ideally the availability should be near 100%, but look out for the trend, if it goes downward you need to act.
Query execution time	Indicates the average time it takes to execute a query.	Seconds
Records fetched	Indicates the total number of records fetched from the query execution.	Number