Db2 Replication Status Test

Replication is a process of maintaining a defined set of data in more than one location. It involves copying designated changes from one location (a source) to another (a target), and synchronizing the data in both locations. The source and target can be in logical servers (such as a DB2 database or a DB2 for OS/390 subsystem or data-sharing group) that are on the same machine or on different machines in a distributed network.

In a high availability environment, the standby servers should always be in sync with the primary database instance. For this, the replication should always be enabled on the primary and the standby servers should be connected to the primary at all times. If the replication fails even for a brief period or if the standby servers are not connected to the primary, the data in the standby servers will not be upto date. To avoid this, it is essential to monitor the replication status of the primary DB2 database instance. The Db2 Replication Status test helps administrators in this regard!

This test reports whether/not the replication process is enabled on the target database instance and also helps administrators figure out if the target database instance is the primary or not. Additionally, this test reports the connection status as well as replication status of the target database instance. Using this test, administrators can easily identify connectivity issues prevalent on the target database server and take remedial measures to resume the connection, if lost at the earliest.

Target of the test : A DB2 database server

Agent deploying the test : An internal/remote agent

Outputs of the test : One set of results for each database created on the target database server instance 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 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.

    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

    Is replication enabled?

    Indicates whether/not replication is enabled on this database.

     

    The values that this measure can report and their corresponding numeric values are listed in the table below:

    Measure Value Numeric Value
    Yes 1
    No 0

    Note:

    By default, the measure reports only the Measure Values provided in the table above to indicate whether/not replication is enabled on the database. In the graph of this measure however, the same is indicated using the numeric equivalents only.

    The detailed diagnosis of this measure lists the IP address of the primary database, the IP address of the standby database and the synchronization mode between the primary and standby database.

    Is primary?

    Indicates whether/not this node is the primary database.

     

    The values that this measure can report and their corresponding numeric values are listed in the table below:

    Measure Value Numeric Value
    Yes 1
    No 0

    Note:

    By default, the measure reports only the Measure Values provided in the table above to indicate whether/not the database is the primary database. In the graph of this measure however, the same is indicated using the numeric equivalents only.

    Connection status

    Indicates the current connection status of this database.

     

    The values that this measure can report and their corresponding numeric values are listed in the table below:

    Measure Value Numeric Value
    Disconnected 0
    Congested 1

    Connected

    		 2

    Note:

    By default, the measure reports only the Measure Values provided in the table above to indicate the current connection status of this database. In the graph of this measure however, the same is indicated using the numeric equivalents only.

    Replication status

    Indicates the current replication status of this database.

     

    The values that this measure can report and their corresponding numeric values are listed in the table below:

    Measure Value Numeric Value
    Disconnected 0
    Disconnected peer 1
    remote catchup pending 2
    remote catchup 3
    local catchup 4
    Peer 5

    Note:

    By default, the measure reports only the Measure Values provided in the table above to indicate the current replication status of this database. In the graph of this measure however, the same is indicated using the numeric equivalents only.