DB2 probe error - probe has to be started for connection test
Article ID: 117130
Updated On:
Products
Issue/Introduction
db2 probe error in IM - Probe has to be started for connection test
Environment
- UIM 20.4
- db2 probe v4.11
Cause
Potential causes:
1. Probe configuration
2. A DSN has been provided that does not exist.
3. DB2INSTANCE not registered yet
4. PATH variable update or correction
5. Need to install the DB2 client runtime (correct version for the given DB2 server version)
Resolution
You MUST set the DB2INSTANCE on the controller (robot.cfg) as shown below.
<environment>
LD_LIBRARY_PATH = /IBM/DB2/sqllib/lib64/
DB2INSTANCE = <DEFAULTINSTANCE>
</environment>
If there is no DB2 'default' instance please refer to 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 db2app.dll 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 need to be added are:
C:\PROGRA~1\IBM\SQLLIB\BIN
C:\PROGRA~1\IBM\SQLLIB\FUNCTION
The path should be in short filename format in order to work correctly.
After setting this, the probe should be able to be started by the controller.
****Note - On the 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
If Linux/UNIX OS:
Example of Robot (controller) environment settings:
<environment>
LD_LIBRARY_PATH = /opt/IBM/db2/V10.1/fp3/lib64
LIBPATH = /opt/IBM/db2/V10.1/fp3/lib64
</environment>
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.
2. For Cause: A DSN has been provided that does not exist
Validate that the DSN that you are connecting to exists, and that you are able to connect to the database using it in Windows ODBC Data Sources (64bit)
Once this is validated, than any time that you run into the Probe has to be started for connection test message, you will have to close out of the probe configuration and deactivate then activate the probe. You will be unable to configure the probe once it gets into this state.
Additional Information
In some cases, we have seen a firewall that blocks the connection to the DB2 server.
Feedback
