DB2 - Problem description
Problem IC96695 | Status: Closed |
CLIDRIVER AND DSDRIVER NOT WORKING ON HP PLATFORM :ERROR "SHARED LIBRARY NOT FOUND 'LIBDB2.SO'" | |
product: | |
DB2 CONNECT / DB2CONNCT / A10 - DB2 | |
Problem description: | |
The instance less clients clidriver and dsdriver throws "shared library not found" error on HP platform for libdb2.so library. When we execute db2support or db2trc or db2cli command, we get this error as below: The libdb2.so library file exists at <install_dir>/lib/libdb2.so. But, commands are unable to find it. The shared library search paths is set to point <install_dir>/lib directory. The problem seems like the system does not search for the shared library in the search path set above. If we run db2support/db2trc/db2cli inside the directory /export/home/dbguest3/sqllib/lib, they it works fine. ( could be because the current directory is on the search path), but if I run the commands from anywhere else, it throws the 'shared library not found' error. So it seems like it doesn't search in the path defined in SHLIB_PATH and LD_LIBRARY_PATH. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * users installing dsdriver/clidriver on HP * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 v101fp4 * **************************************************************** | |
Local Fix: | |
Run the command from <install_dir>/lib directory. | |
available fix packs: | |
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows | |
Solution | |
DB2 v101fp4 contains this fix.No library issues will be seen on using db2cli,db2support,db2trc etc | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 08.10.2013 02.06.2014 02.06.2014 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) | |
10.1.0.4 |