DB2 probe error - probe has to be started for connection test
Document ID :
Last Modified Date :
Show Technical Document Details
CA Unified Infrastructure Management
UIM - DB2:UIMDB2
db2 probe error in IM - probe has to be started for connection test
- UIM 8.5.1
- dbs probe v4.11
- probe configuration
The db2 probe configuration requires information from the DB2 administrator for the correct configuration parameters.
You MUST set the DB2INSTANCE on the controller as below.
LD_LIBRARY_PATH = /IBM/DB2/sqllib/lib64/
DB2INSTANCE = <DEFAULTINSTANCE>
If there is no DB2 'default' instance please check out this link:
How to configure the db2 probe when there is no default DB2 instance
Also,check the environment variables as specified and use the appropriate client version and bit, e.g., 64-bit client for 64-bit server if probe is running remotely versus locally.
The probe not starting and throwing that error on a Windows host is most likely due to the probe not finding the
file usually located in the BIN folder in the run-time client folder.
Ensure that the correct path to the DB2 run-time client is in the PATH environment variable in the controller environment. Usually, the paths that needs to be added are:
After setting this, the probe should be able to be started by the controller.
****Note - On Windows platform after deploying DB2 probe and setting environmental variables, the Robot Watcher service must be restarted in order to initialize DB2 environment variables.
The LD_LIBRARY_PATH to where the db2 probe is deployed is added in the controller probe > Environment tab Instructions
If Linux/UNIX OS:
Example of Robot (controller) environment settings:
LD_LIBRARY_PATH = /opt/IBM/db2/V10.1/fp3/lib64
LIBPATH = /opt/IBM/db2/V10.1/fp3/lib64
Moreover, the output of the commands './db2_monitor' and 'ldd db2_monitor' ran in the db2 probe directory should not point towards a missing library:
'./db2_monitor: error while loading shared libraries: libdb2.so.1: cannot open shared object file: No such file or directory'
This library libdb2.so.1 is located away from the other libraries. Therefore, the environment variable within the Robot controller needs to point to this location for the probe to be able to Activate.
Restart the robot after adding the environment variables.
To test, execute the db2 connection test.
You may also want to reboot and check the probe to make sure it is still operational and you encounter no issues.
Was this information helpful?