Db2 DPF Applications Test

Sometimes a DB2 DPF server may experience performance degradation, not because of blocking, but due to particularly heavy workloads. In such cases, the DBA may conclude that the system cannot handle the workload it is being asked to process while still maintaining acceptable performance. This does not always mean that new indexes must be created or additional hardware deployed. High utilization may not always indicate legitimate activity, problems could stem from inefficient applications or even user-related issues. 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 DPF Applications test.

This test auto-discovers applications running on eachDB2 DPF instance and reports which applications have the most connections open (i.e., processes running in the database). It also identifies the applications that consumed the maximum CPU time and those that generated the highest number of direct read and write operations, helping DBAs pinpoint workload-intensive applications across partitions.

Target of the test : A DB2 database server with DPF enabled

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

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 Frequency

    Refers to the frequency with which detailed diagnosis measures are to be generated for this test. The default is 2: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.
    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