home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Neueste VersionenFixList
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
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IC90671 Status: Geschlossen

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

Produkt:
DB2 CONNECT / DB2CONNCT / 970 - DB2
Problembeschreibung:
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-Zusammenfassung:
**************************************************************** 
* 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                           * 
****************************************************************
Local-Fix:
Explicitly manage thread contexts in the application code.
verfügbare FixPacks:
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

Lösung
First fixed in DB2 V9.7 FP 9
Workaround
Explicitly manage thread contexts in the application code
Bug-Verfolgung
Vorgänger  : APAR is sysrouted TO one or more of the following: IC91953 IC95320 IC96267 
Nachfolger : 
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
06.03.2013
17.06.2013
17.06.2013
Problem behoben ab folgender Versionen (IBM BugInfos)
9.7.FP9
Problem behoben lt. FixList in der Version
9.7.0.8 FixList
9.7.0.9 FixList
9.7.0.9 FixList