DB2 Uptime Test

DB2 uptime refers to the duration the IBM DB2 database remains operational without interruption, ensuring high availability, reliability, and minimal downtime for critical applications and services in enterprise environments.

Monitoring DB2 uptime ensures database availability, detects issues early, and minimizes downtime. It helps maintain service reliability, meet SLAs, support business continuity, and optimize performance by identifying trends, failures, or maintenance needs before they impact users or operations.

The DB2 uptime Test monitors the total uptime, time since last restart etc. These metrics help administrators understand the performance implications of uptime and take preventive actions before the database performance drops.

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 database on the DB2 database server that is currently active

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.

    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.

    Report Manager TIme

    By default, this flag is set to Yes, indicating that, by default, the detailed diagnosis of this test, if enabled, will report the shutdown and reboot times of the device in the manager’s time zone. If this flag is set to No, then the shutdown and reboot times are shown in the time zone of the system where the agent is running(i.e., the system being managed for agent-based monitoring, and the system on which the remote agent is running - for agentless monitoring).

    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

    Has server restarted?

    Indicates whether the database server has been rebooted since the last measurement period or not.

    Number

    If the value of this measure is No, it indicates that the Postgres database server has not restarted. The value Yes on the other hand implies that the Postgres database server has indeed restarted.

    The values reported by this measure and its numeric equivalents are mentioned in the table below:

    Measure Value Numeric Value
    Yes 1
    No 0

    Note:

    By default, this measure reports the value Yes or No to indicate whether a Postgres database server has restarted. The graph of this measure however, represents the same using the numeric equivalents – 0 or 1.

    Uptime since last measure

    Indicates the time period that the database server has been up since the last time this test ran.

    Sec

    If the server has not been rebooted during the last measurement period and the agent has been running continuously, this value will be equal to the measurement period. If the server was rebooted during the last measurement period, this value will be less than the measurement period of the test. For example, if the measurement period is 300 secs, and if the server was rebooted 120 secs back, this metric will report a value of 120 seconds. The accuracy of this metric is dependent on the measurement period - the smaller the measurement period, greater the accuracy.

    Uptime

    Indicates the total time that the server has been up since its last reboot.

    Sec

    This measure displays the number of years, months, days, hours, minutes and seconds since the last reboot. Administrators may wish to be alerted if a server has been running without a reboot for a very long period. Setting a threshold for this metric allows administrators to determine such conditions.

    Is under maintenance?

    Indicates whether/not the server is under maintenance.

     

    The values reported by this measure and their numeric equivalents are available in the table below:

    Measure Value Numeric Value
    No 0
    Yes 1

    Note:

    By default, this measure reports the above-mentioned Measure Values while indicating whether the server is under maintenance or not. However, in the graph of this measure, states will be represented using the corresponding numeric equivalents only - i.e., 0 or 1.