ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

How to configure the db2 probe when there is no default DB2 instance

book

Article ID: 33893

calendar_today

Updated On:

Products

DX Unified Infrastructure Management (Nimsoft / UIM) NIMSOFT PROBES Unified Infrastructure Management for Mainframe CA Unified Infrastructure Management On-Premise (Nimsoft / UIM) CA Unified Infrastructure Management SaaS (Nimsoft / UIM)

Issue/Introduction

How do you configure the db2 probe if you do not have default instances and do not want to create a 'default' instance on your DB2 server?

Environment

  • UIM Server:  Any supported release
  • db2:  Any version 

Resolution

The db2 probe Help documentation indicates the following:

"To access DB2 connectivity has to be set. That means for default local instance DB2INSTANCE has to be set. Remote or additional local instances have to be cataloged in the DB2 node directory. Monitored databases have to be cataloged in the database directory."

It IS possible to monitor DB2 instances in environments where there is no default DB2 instance. The probe only requires that the DB2INSTANCE and DB2INSTDEF variables be set.

In the robot environment where the db2 probe is installed, set the variable DB2INSTANCE to any existing instance on the monitored DB2 server in the robot environment.

You would configure this through the controller GUI:


The DB2INSTDEF variable is set at the system level by executing the following commands (where your db2 default instance is installed):

 

On Linux/UNIX:

./home/db2inst1/sqllib/db2profile  

db2set DB2INSTDEF=<instanceName> -g

 

On Windows:

db2set DB2INSTDEF=<instanceName> -g

Once the DB2INSTDEF variable is set on the db2 system, restart the robot service on the server where the db2 probe is installed.

You can choose any db2 instance to be your default instance. The db2 probe will then use this instance to connect but will monitor all the other instances.

Alternatively, for some situations, you could create a local "dummy " instance. Then this instance can be used as a 'gateway.' Once the gateway is created your DBA would need to catalogue the databases to be monitored as local.

Attachments