|
Problem IC69396
|
Status: Geschlossen |
DB2 CLIENT TRAPPED IN FUNCTION SQLEUCLOCKCONNECTION USING MSDTC |
| Produkt: |
DB2 FOR LUW / DB2FORLUW / 970 - 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: *
* Windows applications using MSDTC *
****************************************************************
* 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 to v9.7.3 *
**************************************************************** |
| Local-Fix: |
|
| verfügbare FixPacks: |
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
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 |
|
| Workaround |
keiner bekannt / siehe Local-Fix |
| Bug-Verfolgung |
Vorgänger : APAR is sysrouted TO one or more of the following: IC69397
Nachfolger : |
| Weitere Daten |
Datum - Problem gemeldet :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
| 22.06.2010
16.09.2010
16.09.2010 |
| Problem behoben ab folgender Versionen (IBM BugInfos) |
9.7.3
|
| Problem behoben lt. FixList in der Version |
| 9.7.0.3
|
 |
| 9.7.0.3
|
|
