DB2 instance monitoring for multiple instances with different database ports

Products

• DX Unified Infrastructure Management (Nimsoft / UIM)

Issue/Introduction

Technical requirements often require monitoring multiple IBM DB2 instances on a single server where each instance uses a different database port. This includes scenarios where no default instance is configured or where secondary instances must be cataloged specifically for probe connectivity. How do I monitor a server that has 2 instances which also have different database ports?

Environment

• DX UIM 23.4.*
• db2 probe (all versions)
• IBM DB2 Server

Cause

Guidance

Resolution

To enable dual monitoring for multiple instances on the same server, follow these sequential steps to catalog the instances and configure the probe environment.

1. Catalog the primary and secondary instances Work with the DB2 Database Administrator (DBA) to catalog each instance node locally.

   • For instance 1, create a connection using its specific catalog node and user.
   • For instance 2, proceed with cataloging the instance locally. Note that this secondary instance must have a distinct user for the probe connection.

2. Configure environment variables in the Robot Controller Open the Infrastructure Manager (IM) or Admin Console (AC) and navigate to the controller probe on the monitored robot. Under the Environment tab, set or update the following:

   • DB2INSTANCE: Set this to any existing valid instance on the server.
   • LD_LIBRARY_PATH: Ensure this variable includes the paths to both 32-bit and 64-bit sqllib folders for the required instances. Example: /apps/IBM/db2/####/home/sqllib/lib32:/apps/IBM/db2/####/home/sqllib/lib64

3. Set the DB2INSTDEF variable Execute the following commands at the operating system level to ensure the DB2 client recognizes the default definitions:

   • Linux/UNIX:
      

     ./home/[instance_name]/sqllib/db2profiledb2set DB2INSTDEF=[instance_name] -g

   • Windows:
     
     
     

     db2set DB2INSTDEF=[instance_name] -g

4. Restart the Robot Watcher service Restart the Nimsoft Robot Watcher service on the server where the db2 probe is installed. This step is mandatory to initialize the new environment variables and library paths.

5. Verify connectivity via Command Line Before configuring the probe GUI, use the DB2 command line to ensure the secondary instance is reachable through the newly cataloged node and port.

6. Create multiple Resource Blocks in the probe In the db2 probe configuration UI, create a separate resource for each instance. Provide the specific catalog node, username, and database port (e.g., port 28060 for the first instance and port 28061 for the second) for each connection.

Additional Information

• To retrieve logs for further troubleshooting, set the db2 probe log level to 5 and review the db2_monitor.log.
• For further assistance,Contact Broadcom support
• Related KB: How to configure the db2 probe when there is no default DB2 instance