Db2 Applications Test

Sometimes the database performs poorly due, not to blocking, but to particularly heavy loads. Often the DBA will determine that the database simply cannot support the work that it is being asked to do and maintain adequate performance. This does not necessarily mean it is time to create more indexes or throw more hardware at the problem. One cannot always assume that periods of high utilization represent legitimate work. There could be problems in the applications that are running, or even problems caused by the user. To monitor the statistics pertaining to the different applications executing on a Db2 UDB Database server and their usage and identifies which program has more connections open to (i.e., processes running in) the Db2 database, eG enterprise offers the Db2 Applications test.

This test auto-discovers applications running on each DB2 UDB instance on the target DB2 server, and reports which application has more connections open to (i.e., processes running in) the Db2 database. This test also reveals the application that consumed CPU for maximum time and required maximum number of direct read and write operations.

Target of the test : A DB2 database server

Agent deploying the test : An internal agent

Outputs of the test : One set of results for each application running on every database on the DB2 database server that is 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 and Confirm 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 UDB server. Specify the name of the database in the Database text box.
Include DB	Specify the list of databases that you wish to monitor in a comma-seperated list in the Include DB text box. By default this is set to ALL.
Exclude DB	Specify the list of databases that you wish to exclude from monitoring in a comma-seperated list in the Exclude DB text box. By default this is set to NONE.
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.
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	The trust store file contains certificates from trusted Certificate Authorities (CAs). These certificates are used by eG agent to verify the authenticity of servers hosting DB2 UDB and establish a secure connection with the server using SSL. Specify the filename for Trust store file in Trust Store file name text box.
Trust Store Password	The trust store password is the passphrase or key used to encrypt and decrypt the trust store file. This password is required by the eG Agent when it needs to access the trust store file to establish secure connections. Specify the password in Trust Store password text box.
Confirm Password	Confirm the Password by retyping it in the Confirm Password text box.
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.

Measures made by the test:
Measurement	Description	Measurement Unit	Interpretation
Connection count	Indicates the number of connections that are currently established for running this application on this database instance.	Number
Maximum CPU time	Indicates the maximum time taken by CPU for executing this application.	Seconds	Compare the value of this measure across the applications to find out which application took prolonged CPU time. The detailed diagnosis of this measure reveals the application id, name of user who runs each application, IP address of the user, CPU time, count of reads and writes and SQL text.
Average CPU time	Indicates the average time taken by CPU for executing this application.	Seconds
Maximum direct reads	Indicates the maximum number of direct reads by this application.	Number	A high value over a period of time may be indicative of a performance bottleneck. The detailed diagnosis of this measure reveals the application id, name of user who runs each application, IP address of the user, CPU time, count of reads and writes and SQL text.
Average direct reads	Indicates the average number of direct reads by this application per second.	Reads/second
Maximum direct writes	Indicates the maximum number of direct writes by this application.	Number	The detailed diagnosis of this measure reveals the application id, name of user who runs each application, IP address of the user, CPU time, count of reads and writes and SQL text.
Average direct writes	Indicates the average number of direct reads by this application per second.	Writes/second