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 IC69397 Status: Geschlossen

DB2 CLIENT TRAPPED IN FUNCTION SQLEUCLOCKCONNECTION USING MSDTC

Produkt:
DB2 FOR LUW / DB2FORLUW / 980 - DB2
Problembeschreibung:
DB2 client trap at disconnect with the following stack. 
 
db2app!sqleUClockConnection+0x38 
[T:\db2_v97fp2\nt32\n100304\engn\include\sqleu_client_inlines.h 
@ 679] 
db2app!XADTCObject::BlockOnEvent+0x175 [sqlxadtc.C @ 1085] 
db2app!XADTCObject::Disconnect+0x1b2 [sqlxadtc.C @ 920] 
db2app!sqlxaDTCDisconnect+0xf2 [sqlxadtc.C @ 447] 
db2app!CLI_sqlDisconnect+0x406 [clisql.C @ 2781] 
db2app!SQLDisconnect2+0x339 [cliconn.C @ 6596] 
db2app!SQLDisconnect+0x769 [cliconn.C @ 6396] 
mscorwks!Thread::EndThreadAffinity+0xa8 
 
 
The trap can occur in multi threaded setup. The trap can occur 
when a thread tries to access the connection to process a 
disconnect request. But another thread had already cleaned up 
connection resources because of an error condition.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* User using MSDTC as TM                                       * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* DB2 client trap at disconnect with the following stack.      * 
*                                                              * 
*                                                              * 
*                                                              * 
* db2app!sqleUClockConnection+0x38                             * 
*                                                              * 
* [T:\db2_v97fp2\nt32\n100304\engn\include\sqleu_client_inlines. 
* @ 679]                                                       * 
*                                                              * 
* db2app!XADTCObject::BlockOnEvent+0x175 [sqlxadtc.C @ 1085]   * 
*                                                              * 
* db2app!XADTCObject::Disconnect+0x1b2 [sqlxadtc.C @ 920]      * 
*                                                              * 
* db2app!sqlxaDTCDisconnect+0xf2 [sqlxadtc.C @ 447]            * 
*                                                              * 
* db2app!CLI_sqlDisconnect+0x406 [clisql.C @ 2781]             * 
*                                                              * 
* db2app!SQLDisconnect2+0x339 [cliconn.C @ 6596]               * 
*                                                              * 
* db2app!SQLDisconnect+0x769 [cliconn.C @ 6396]                * 
*                                                              * 
* mscorwks!Thread::EndThreadAffinity+0xa8                      * 
*                                                              * 
*                                                              * 
*                                                              * 
*                                                              * 
*                                                              * 
* The trap can occur in multi threaded setup. The trap can     * 
* occur                                                        * 
* when a thread tries to access the connection to process a    * 
*                                                              * 
* disconnect request. But another thread had already cleaned   * 
* up                                                           * 
* connection resources because of an error condition.          * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade client to v9.8.4                                     * 
****************************************************************
Local-Fix:
verfügbare FixPacks:
DB2 Version 9.8 Fix Pack 4 for AIX and Linux
DB2 Version 9.8 Fix Pack 5 for AIX and Linux

Lösung
Add check to make sure connection is not freed before freeing 
resources.
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
22.06.2010
11.09.2011
11.09.2011
Problem behoben ab folgender Versionen (IBM BugInfos)
9.8.4
Problem behoben lt. FixList in der Version
9.8.0.4 FixList