|
Problem IC97841
|
Status: Closed |
CLIDRIVER AND DSDRIVER NOT WORKING ON HP PLATFORM :ERROR "SHARED LIBRARY NOT FOUND 'LIBDB2.SO'" |
| product: |
DB2 FOR LUW / DB2FORLUW / A50 - 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: *
* DSDRIVER AND CLIDRIVER on HP platform *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to db2_v97fp9 or db2_v101fp4 or db_v105fp3 *
**************************************************************** |
| Local Fix: |
Run the command from <install_dir>/lib directory. |
| available fix packs: |
DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 9 for Linux, UNIX, and Windows
|
| Solution |
DB2 v97fp9
DB2 v101fp4
DB2 v105fp3 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 21.11.2013
08.09.2014
08.09.2014 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP9
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.5.0.4
|
 |
