|
Problem IC62672
|
Status: Geschlossen |
XA ERROR MESSAGES REPORTED IN SERVER SIDE DB2DIAG.LOG |
| Produkt: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problembeschreibung: |
db2diag.log on the server contains the following message:
FUNCTION: DB2 UDB, relation data serv, sqlrr_xa_tm_post,
probe:1011
MESSAGE : pCallinfo->xid:
DATA #1 : Hexdump, 140 bytes
0x0FFFFFFFFFFEF8F8 : 0044 5443 0000 0010 0000 0030 1F53 5A3A
.DTC.......0.SZ:
0x0FFFFFFFFFFEF908 : A40E CB4D 83AC 1192 BFEC 57EB 7EE7 5E1B
...M......W.~.^.
0x0FFFFFFFFFFEF918 : 6CAD 0F41 9ED2 02BE D0BB 51D9 814C 8B95
l..A......Q..L..
0x0FFFFFFFFFFEF928 : BB1E A348 A971 FE82 16E6 C36C 89BE F33E
...H.q.....l...>
0x0FFFFFFFFFFEF938 : 25C4 434F A492 A1F8 3D56 1712 0000 0000
%.CO....=V......
0x0FFFFFFFFFFEF948 : 0000 0000 0000 0000 0000 0000 0000 0000
................
0x0FFFFFFFFFFEF958 : 0000 0000 0000 0000 0000 0000 0000 0000
................
0x0FFFFFFFFFFEF968 : 0000 0000 0000 0000 0000 0000 0000 0000
................
0x0FFFFFFFFFFEF978 : 0000 0000 0000 0000 0000 0000
............
FUNCTION: DB2 UDB, data protection, sqlpxend, probe:750
MESSAGE : The provided xid is not associated with the
applcation.
DATA #1 : Hexdump, 140 bytes
0x0FFFFFFFFFFEF8F8 : 0044 5443 0000 0010 0000 0030 F515 6458
.DTC.......0..dX
0x0FFFFFFFFFFEF908 : 1D3F 224D AC6F FF23 9677 D8B8 7EE7 5E1B
.?'M.o.#.w..~.^.
0x0FFFFFFFFFFEF918 : 6CAD 0F41 9ED2 02BE D0BB 51D9 D806 599A
l..A......Q...Y.
0x0FFFFFFFFFFEF928 : 4CCF 2341 84B0 B403 D0C0 1A25 D359 ABE3
L.#A.......%.Y..
0x0FFFFFFFFFFEF938 : A124 6843 8949 33DD 8986 3B22 0000 0000
.$hC.I3...;'....
0x0FFFFFFFFFFEF948 : 0000 0000 0000 0000 0000 0000 0000 0000
................
0x0FFFFFFFFFFEF958 : 0000 0000 0000 0000 0000 0000 0000 0000
................
0x0FFFFFFFFFFEF968 : 0000 0000 0000 0000 0000 0000 0000 0000
................
0x0FFFFFFFFFFEF978 : 0000 0000 0000 0000 0000 0000
............
2008-06-19-08.43.07.091568-240 I6931016A157 LEVEL: Severe
PID:823456 TID:1 NODE:000 Title: SQLP_ACB
Dump File:/home/svtdbm4/sqllib/db2dump/8234561.00
The above error messages in server side db2diag.log are caused
by XA protocol violation.
Fix is on DB2 Client only specific for windows running XA
application and using MSDTC as TM. The error message was caused
by inocorrect error handling on failing XA_REG call. DB2 LUW
Client was sending XA_END and XA_ROLLBACK even if XA_REG was
failing.
After applying the fix, client will not send XA_END and
XA_ROLLBACK if an application fails to register a transaction. |
| Problem-Zusammenfassung: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* db2diag.log on the server contains the following message: *
* *
* FUNCTION: DB2 UDB, relation data serv, sqlrr_xa_tm_post, *
* probe:1011 *
* MESSAGE : pCallinfo->xid: *
* DATA #1 : Hexdump, 140 bytes *
* *
* 0x0FFFFFFFFFFEF8F8 : 0044 5443 0000 0010 0000 0030 1F53 5A3A *
* .DTC.......0.SZ: *
* 0x0FFFFFFFFFFEF908 : A40E CB4D 83AC 1192 BFEC 57EB 7EE7 5E1B *
* ...M......W.~.^. *
* 0x0FFFFFFFFFFEF918 : 6CAD 0F41 9ED2 02BE D0BB 51D9 814C 8B95 *
* l..A......Q..L.. *
* 0x0FFFFFFFFFFEF928 : BB1E A348 A971 FE82 16E6 C36C 89BE F33E *
* ...H.q.....l...> *
* 0x0FFFFFFFFFFEF938 : 25C4 434F A492 A1F8 3D56 1712 0000 0000 *
* %.CO....=V...... *
* 0x0FFFFFFFFFFEF948 : 0000 0000 0000 0000 0000 0000 0000 0000 *
* ................ *
* 0x0FFFFFFFFFFEF958 : 0000 0000 0000 0000 0000 0000 0000 0000 *
* ................ *
* 0x0FFFFFFFFFFEF968 : 0000 0000 0000 0000 0000 0000 0000 0000 *
* ................ *
* 0x0FFFFFFFFFFEF978 : 0000 0000 0000 0000 0000 0000 *
* ............ *
* *
* FUNCTION: DB2 UDB, data protection, sqlpxend, probe:750 *
* MESSAGE : The provided xid is not associated with the *
* applcation. *
* DATA #1 : Hexdump, 140 bytes *
* 0x0FFFFFFFFFFEF8F8 : 0044 5443 0000 0010 0000 0030 F515 6458 *
* .DTC.......0..dX *
* 0x0FFFFFFFFFFEF908 : 1D3F 224D AC6F FF23 9677 D8B8 7EE7 5E1B *
* .?'M.o.#.w..~.^. *
* 0x0FFFFFFFFFFEF918 : 6CAD 0F41 9ED2 02BE D0BB 51D9 D806 599A *
* l..A......Q...Y. *
* 0x0FFFFFFFFFFEF928 : 4CCF 2341 84B0 B403 D0C0 1A25 D359 ABE3 *
* L.#A.......%.Y.. *
* 0x0FFFFFFFFFFEF938 : A124 6843 8949 33DD 8986 3B22 0000 0000 *
* .$hC.I3...;'.... *
* 0x0FFFFFFFFFFEF948 : 0000 0000 0000 0000 0000 0000 0000 0000 *
* ................ *
* 0x0FFFFFFFFFFEF958 : 0000 0000 0000 0000 0000 0000 0000 0000 *
* ................ *
* 0x0FFFFFFFFFFEF968 : 0000 0000 0000 0000 0000 0000 0000 0000 *
* ................ *
* 0x0FFFFFFFFFFEF978 : 0000 0000 0000 0000 0000 0000 *
* ............ *
* *
* 2008-06-19-08.43.07.091568-240 I6931016A157 LEVEL: Severe *
* PID:823456 TID:1 NODE:000 Title: SQLP_ACB *
* Dump File:/home/svtdbm4/sqllib/db2dump/8234561.00 *
* *
* The above error messages in server side db2diag.log are *
* caused by XA protocol violation. *
* *
* Fix is on DB2 Client only specific for windows running XA *
* application and using MSDTC as TM. The error message was *
* caused by incorrect error handling on failing XA_REG call. *
* DB2 LUW Client was sending XA_END and XA_ROLLBACK even if *
* XA_REG was *
* failing. *
* *
* After applying the fix, client will not send XA_END and *
* XA_ROLLBACK if an application fails to register a *
* transaction. *
****************************************************************
* RECOMMENDATION: *
* Update the fixpack with the APAR. *
**************************************************************** |
| Local-Fix: |
|
| verfügbare FixPacks: |
DB2 Version 9.7 Fix Pack 1 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
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 9a 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 10 for Linux, UNIX, and Windows
|
| Lösung |
Problem was first fixed in DB2 UDB Version 9.7 Fix Pack 1. |
| Workaround |
keiner bekannt / siehe Local-Fix |
| Weitere Daten |
Datum - Problem gemeldet :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
| 20.08.2009
24.02.2010
11.07.2011 |
| Problem behoben ab folgender Versionen (IBM BugInfos) |
9.7.FP1
|
| Problem behoben lt. FixList in der Version |
| 9.7.0.1
|
 |
