home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Latest versionsfixlist
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IC84299 Status: Closed

CANNOT CONNECT TO DATABASE FROM CLP WHEN USING DB2DSDRIVER.CFG. DB2DIAG.LOG
ERROR: CANNOT OPEN SHARED OBJECT LIBDB2CLIXML4C.SO

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
When db2dsdriver.cfg is configured to connect to the database 
from DB2 V9.7 FP5 CLP, the connection may not be established 
neither error is reported on the CLP window. 
 
The error message like below appears in the db2diag.log: 
 
2011-12-27-10.04.55.802873-300 I200563E1296        LEVEL: Error 
PID     : 664                  TID  : 140332108551936PROC :db2bp 
INSTANCE: db2psc               NODE : 000 
FUNCTION: DB2 Common, OSSe, OSSHLibrary::load, probe:90 
MESSAGE : ECF=0x90000076=-1879048074=ECF_LIB_CANNOT_LOAD 
Cannot load the specified library DATA #1 : String, 98 bytes 
/opt/ibm/db2/V9.7/lib/libdb2clixml4c.so: cannot open shared 
object file: No such 
 file or directory 
CALLSTCK: (Static functions may not be resolved correctly, as 
they are resolved 
to the nearest symbol) 
  [0] 0x00007FA19BD3A6FE pdOSSeLoggingCallback + 0x100 
  [1] 0x00007FA19A6B6F46 
/home/db2psc/sqllib/lib64/libdb2osse.so.1 +0x1D3F46 
  [2] 0x00007FA19A6B8762 ossLog + 0xA6 
  [3] 0x00007FA19A6C328F _ZN11OSSHLibrary4loadEPKcm + 0x237 
  [4] 0x00007FA19C055ADC CLI_coLoadXml4cLib + 0x1CE 
  [5] 0x00007FA19C2CA7D7 _ZN9rccConfig7loadXmlEP5sqlcaPc + 0x1CB 
  [6] 0x00007FA19C2D425A 
_ZN10rccDBEntry19getAltSrvrFromCacheEP7rccListP5sqlca + 0x144 
  [7] 0x00007FA19C2D581E 
_ZN10rccDBEntry28getEffectiveAlternateSrvListEPcPbPP7rccListP5sq 
lca + 0x172
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Users connecting to database from command line with using    * 
* DB2DSDRIVER.CFG                                              * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* CANNOT CONNECT TO DATABASE FROM CLP WHEN USING               * 
* DB2DSDRIVER.CFG.DB2DIAG.LOG ERROR: CANNOT OPEN SHARED OBJECT * 
* LIBDB2CLIXML4C.SO                                            * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.1 Fix Pack 1                       * 
****************************************************************
Local Fix:
Workaround is to manually create a softlink for lib pointing to 
lib64 (in 64 bit clients) or to lib32(in 32 bit clients), 
present under install path eg. /opt/ibm/db2/V9.7 
 
To create a softlink for the lib directory you must first change 
directory to the install path and then create the softlink: 
      -traverse to the install path 
      -create soft link 
 
For example, assume your client is installed in 
/opt/ibm/db2/v9.7 and you encounter the error.  Use the 
following commands to create the softlink on the client: 
 
-->64-bit client 
        cd  /opt/ibm/db2/v9.7 
        sudo ln -s lib64 lib 
 
-->32-bit client 
        cd /opt/ibm/db2/v9.7 
        sudo ln -s lib32 lib
available fix packs:
DB2 Version 10.1 Fix Pack 1 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows

Solution
Problem first fixed in DB2 Version 10.1 Fix Pack 1
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
13.06.2012
20.11.2012
20.11.2012
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.1 FixList
10.5.0.1 FixList