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

MULTI-THREADED APPLICATIONS USING BOTH ESQL/C AND CLI INTERFACES MAY
EXPERIENCE HANGS OR CRASHES WHEN NOT USING EXPLICIT CONTEXT

product:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problem description:
Multi-threaded applications that make use of ESQL/C in some 
threads 
and CLI in others and do not explicitly manage their own 
contexts 
may experience hangs or crashes. 
 
Hangs will typically have no other threads in active CLI or 
ESQL/C 
code, with one ESQL/C thread having the stack: 
 
NOTE: On Windows, stacks need to be determined from user mode 
crash dump files with the correct debugging symbols. Stacks 
logged in the Windows event logs will not be accurate. 
 
ntdll!KiFastSystemCallRet 
ntdll!ZwWaitForSingleObject 
kernel32!WaitForSingleObjectEx 
kernel32!WaitForSingleObject 
db2sys!sqloxconflict_LONG 
db2sys!sqloxltc_app 
db2app!sqlastrt 
db2app!sqlastrt 
... 
 
Crashes will be in a CLI thread with a typical stack: 
 
sqlak_callbComplete 
sqljrParseRdbCmmReply 
sqljrParse 
sqljrDrdaArCommit 
CLI_sqlCommit 
SQLTransact2 
SQLDisconnect2 
SQLDisconnect 
... 
 
(Notably here we see CLI functions calling an ESQL/C call back 
function.) 
 
This APAR fix will address the conditions resulting in these two 
described events.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Multi-threaded applications using both ESQL/C and CLI        * 
* interfaces                                                   * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 V10.5 FP 3 or higher                          * 
****************************************************************
Local Fix:
Explicitly manage thread contexts in the application code.
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
First fixed in DB2 V10.5 FP3
Workaround
Explicitly manage thread contexts in the application code
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
27.08.2013
27.02.2014
27.02.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
10.5.0.4 FixList