|
Problem IC85525
|
Status: Closed |
XID COLUMN HAS INCORRECT DATA IN LOCK_PARTICIPANTS TABLE OF A TABLE LOCKING EVENT MONITOR |
| product: |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 |
| Problem description: |
When an XA transaction is involved in a deadlock, lock timeout
or lock wait and is recorded by a LOCKING event monitor that
writes to a TABLE target (rather than an UNFORMATTED EVENT
TABLE), the XID value recorded by the event monitor has
incorrect data.
This issue does not affect XA transactions being recorded by a
LOCKING UNFORMATTED EVENT TABLE event monitor. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* Anybody using XA and a LOCKING TABLE event monitor *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to Version 10.1 Fix Pack Y *
**************************************************************** |
| Local Fix: |
Use an UNFORMATTED EVENT TABLE LOCKING event monitor |
| available fix packs: |
DB2 Version 10.1 Fix Pack 1 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows
|
| Solution |
Problem was first fixed in Version 10.1 Fix Pack Y |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 25.07.2012
31.10.2012
31.10.2012 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.1.0.1
|
 |
| 10.5.0.1
|
|
