DB2 CONNECT / DB2CONNCT / 970 - DB2

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.

**************************************************************** 
* USERS AFFECTED:                                              * 
* Multi-threaded applications using both ESQL/C and CLI        * 
* interfaces                                                   * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 V9.7 FP 9 or higher                           * 
****************************************************************

Explicitly manage thread contexts in the application code.

DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
 

First fixed in DB2 V9.7 FP 9

Explicitly manage thread contexts in the application code

forerunner  : APAR is sysrouted TO one or more of the following: IC91953 IC95320 IC96267 
follow-up : 

Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :

06.03.2013
17.06.2013
17.06.2013

9.7.FP9