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 IC95527 Status: Closed

APPLICATION CAN CRASH WHEN USING DB2DSDRIVER.CFG AND IF THE SRVRLST.XML
FILE CANNOT BE CREATED

product:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problem description:
An application using the db2dsdriver.cfg (for example CLI) may 
crash if the srvrlst.xml file cannot be created.  This file will 
exist in the 'cfgcache' subdirectory for the instance or for the 
driver. 
 
If there is no write permission for the application user for 
example, then the file cannot be created. 
 
When the application crashes it can produce a coredump file. 
The db2diag.log may contain a call stack as follows: 
 
CALLSTCK: (Static functions may not be resolved correctly, as 
they are resolved to the nearest symbol) 
  [0] 0x00007F8A6A249C39 pdOSSeLoggingCallback + 0x219 
  [1] 0x00007F8A686410AB 
/home/db2inst1/sqllib/lib64/libdb2osse.so.1 + 0x2070AB 
  [2] 0x00007F8A68642A23 ossLogSysRC + 0xB3 
  [3] 0x00007F8A68635400 
/home/db2inst1/sqllib/lib64/libdb2osse.so.1 + 0x1FB400 
  [4] 0x00007F8A6863281D ossErrorAnalysis + 0x2D 
  [5] 0x00007F8A6ABA6C91 sqloSystemErrorHandler + 0x6A1 
  [6] 0x00007F8A6AD48A31 sqloopenp + 0x1461 
  [7] 0x00007F8A6A864163 _ZN9rccConfig7loadXmlEP5sqlcaPc + 0x173 
  [8] 0x00007F8A6A86A565 
_ZN10rccDBEntry18setAltSrvrsInCacheEP7rccListP5sqlca + 0xE5 
  [9] 0x00007F8A6AAD388C /home/db2inst1/sqllib/lib64/libdb2.so.1 
+ 0xE4E88C 
  [10] 0x00007F8A6AAD3586 
_Z16sqljrParseSrvlstP14db2UCinterfacetPb + 0x266 
  [11] 0x00007F8A6AAE3DE5 
_Z18sqljrParseAccrdbrmP14db2UCinterface + 0xC05 
  [12] 0x00007F8A6AB07549 _Z10sqljrParseP14db2UCinterface + 0xB9 
  [13] 0x00007F8A6AB01613 
_Z23sqljrDrdaArAuthenticateP14db2UCinterfacelPj + 0x233 
  [14] 0x00007F8A6A9CE8FF 
_Z20sqlexAppAuthenticateP14db2UCinterface + 0x5CF 
  [15] 0x00007F8A6AAF05BC 
_Z18sqljrDrdaArConnectP14db2UCinterface + 0x9C 
  [16] 0x00007F8A6A9BC6CB _Z16sqleUCdrdaARinitP14db2UCconHandle 
+ 0x6B 
  [17] 0x00007F8A6A2B3819 sqleUCappConnect + 0x479 
  [18] 0x00007F8A6A1E0002 
_Z14CLI_sqlConnectP15CLI_CONNECTINFOP5sqlcaP19CLI_ERRORHEADERINF 
O + 0x752 
  [19] 0x00007F8A6A1D2EC0 
_Z11SQLConnect2P15CLI_CONNECTINFOPhsS1_sS1_sS1_sh + 0x460 
  [20] 0x00007F8A6A1CF7A6 
_Z17SQLDriverConnect2P15CLI_CONNECTINFOPvPhsS2_sPsthhP19CLI_ERRO 
RHEADERINFO + 0x10946 
  [21] 0x00007F8A6A5543B7 SQLDriverConnectW + 0x8A7
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Linux/Unix                                                   * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Update to 10.5.0.3                                           * 
****************************************************************
Local Fix:
Modify the permission to cfgcache to allow the creation of the 
file.  If the file does not already exist on an instance based 
client use the CLP to perform a connection to the database which 
should then create the file.
available fix packs:
DB2 Version 10.5 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 3a for Linux, UNIX, and Windows
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
Problem Fixed In 10.5.0.3
Workaround
See Local Fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
27.08.2013
06.03.2014
06.03.2014
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.5.0.3 FixList
10.5.0.3 FixList