In DB2 10.1, burst of DIA8039C errors may be seen after
deadlock. This is because, DB2 is not ending the XA transaction
who is victim of deadlock.
DB2diag.log may look like this:
1> Deadlock victim:
2013-12-10-13.35.18.374620-300 E45322933A1340 LEVEL:
Warning
PID : 9044452 TID : 22362 PROC :
db2sysc 0
INSTANCE: db2mudb NODE : 000 DB :
DB2PONLD
APPHDL : 0-1236 APPID:
165.115.107.246.44209.131210183509
AUTHID : DTAPODS HOSTNAME: r59s3t2
EDUID : 22362 EDUNAME: db2agent (SMYARD) 0
FUNCTION: DB2 UDB, database monitor,
sqmLockEvents::collectLockEvent, probe:272
MESSAGE : ADM5506W The current unit of work was involved in an
unresolved
contention for use of an object. The type of the event
is:
"Deadlock". The identifier of the lock on which this
event happened
is: "001600050000000017CE000952". The timestamp of the
event is:
"2013-12-10-13.35.18.374379". The identifier of the
member at which
the event happened, and the identifier of the event
is: "137". The
affected application is named "db2jcc_application" The
application is
associated with the workload named
"SYSDEFAULTUSERWORKLOAD". The
application identifier is:
"165.115.107.246.44209.131210183509". The
identifier of the member on which the application is
running is: "0".
The role that this application plays with respect to
this lock is:
"Victim".
2. Deadlock participant:
2013-12-10-13.35.18.375769-300 E45325146A1345 LEVEL:
Warning
PID : 9044452 TID : 28567 PROC :
db2sysc 0
INSTANCE: db2mudb NODE : 000 DB :
DB2PONLD
APPHDL : 0-495 APPID:
165.115.107.246.54179.131210170453
AUTHID : DTAPODS HOSTNAME: r59s3t2
EDUID : 28567 EDUNAME: db2agent (SMYARD) 0
FUNCTION: DB2 UDB, database monitor,
sqmLockEvents::collectLockEvent, probe:272
MESSAGE : ADM5506W The current unit of work was involved in an
unresolved
contention for use of an object. The type of the event
is:
"Deadlock". The identifier of the lock on which this
event happened
is: "001600050000000017D5001052". The timestamp of the
event is:
"2013-12-10-13.35.18.374379". The identifier of the
member at which
the event happened, and the identifier of the event
is: "137". The
affected application is named "db2jcc_application" The
application is
associated with the workload named
"SYSDEFAULTUSERWORKLOAD". The
application identifier is:
"165.115.107.246.54179.131210170453". The
identifier of the member on which the application is
running is: "0".
The role that this application plays with respect to
this lock is:
"Participant".
3. -911 was raised and thrown back up to the user application to
inform them that the XA transaction is dead.
That means stop trying to end and join to it, as it has been
rolled back and is now gone
2013-12-10-13.35.18.375289-300 I45324274A871 LEVEL: Error
PID : 9044452 TID : 22362 PROC :
db2sysc 0
INSTANCE: db2mudb NODE : 000 DB :
DB2PONLD
APPHDL : 0-1236 APPID:
165.115.107.246.44209.131210183509
AUTHID : DTAPODS HOSTNAME: r59s3t2
EDUID : 22362 EDUNAME: db2agent (SMYARD) 0
FUNCTION: DB2 UDB, relation data serv, sqlrr_array_input,
probe:210
DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes
sqlcaid : SQLCA sqlcabc: 136 sqlcode: -911 sqlerrml: 1
sqlerrmc: 2
sqlerrp : SQLRI2CB
sqlerrd : (1) 0x80100002 (2) 0x00000002 (3)
0x00000000
(4) 0x00000000 (5) 0xFFFFFE0C (6)
0x00000000
sqlwarn : (1) (2) (3) (4) (5) (6)
(7) (8) (9) (10) (11)
sqlstate:
4. But application keeps on trying to end , reg(join),
reg(join) over and over again
( note same transaction id over and over )
2013-12-10-13.35.19.792512-300 I45326492A1432 LEVEL:
Warning
PID : 9044452 TID : 22362 PROC :
db2sysc 0
INSTANCE: db2mudb NODE : 000 DB :
DB2PONLD
APPHDL : 0-1236 APPID:
165.115.107.246.44209.131210183509
AUTHID : DTAPODS HOSTNAME: r59s3t2
EDUID : 22362 EDUNAME: db2agent (SMYARD) 0
FUNCTION: DB2 UDB, data protection services, sqlpxend,
probe:1060
MESSAGE : The application is not associated with any XA
transaction. The
transaction to be ended might have been aborted by
this RM. One of
the reason to cause this type of internal abort is
dead lock.
DATA #1 : Hexdump, 140 bytes
0x070000008A7F7088 : 5741 5344 0000 0024 0000 0036 0000 0142
WASD...$...6...B
0x070000008A7F7098 : DDCA 8CE3 0000 0001 0004 8A96 1B89 8CFF
................
0x070000008A7F70A8 : 8673 7EAF 0768 C063 AC01 63F4 FC7B 7B8D
.s~..h.c..c..{{.
0x070000008A7F70B8 : 0000 0142 DDCA 8CE3 0000 0001 0004 8A96
...B............
0x070000008A7F70C8 : 1B89 8CFF 8673 7EAF 0768 C063 AC01 63F4
.....s~..h.c..c.
0x070000008A7F70D8 : FC7B 7B8D 0000 0001 0000 0000 0000 0000
.{{.............
0x070000008A7F70E8 : 0000 0000 0001 0000 0000 0000 0000 0000
................
0x070000008A7F70F8 : 0000 0000 0000 0000 0000 0000 0000 0000
................
0x070000008A7F7108 : 0000 0000 0000 0000 0000 0000
............
5> This results in SQLP_PROTO
2013-12-10-13.35.19.793202-300 I45328504A4326 LEVEL: Error
PID : 9044452 TID : 22362 PROC :
db2sysc 0
INSTANCE: db2mudb NODE : 000 DB :
DB2PONLD
APPHDL : 0-1236 APPID:
165.115.107.246.44209.131210183509
AUTHID : DTAPODS HOSTNAME: r59s3t2
EDUID : 22362 EDUNAME: db2agent (SMYARD) 0
FUNCTION: DB2 UDB, relation data serv, sqlrr_xa_tm_post,
probe:200
MESSAGE : SQLP_PROTO:
DATA #1 : Hex, PD_TYPE_INTERNAL_10, 752 bytes
0x070000008A7F7088 : 5741 5344 0000 0024 0000 0036 0000 0142
WASD...$...6...B
0x070000008A7F7098 : DDCA 8CE3 0000 0001 0004 8A96 1B89 8CFF
................
0x070000008A7F70A8 : 8673 7EAF 0768 C063 AC01 63F4 FC7B 7B8D
.s~..h.c..c..{{.
0x070000008A7F70B8 : 0000 0142 DDCA 8CE3 0000 0001 0004 8A96
...B............
0x070000008A7F70C8 : 1B89 8CFF 8673 7EAF 0768 C063 AC01 63F4
.....s~..h.c..c.
0x070000008A7F70D8 : FC7B 7B8D 0000 0001 0000 0000 0000 0000
.{{.............
0x070000008A7F70E8 : 0000 0000 0001 0000 0000 0000 0000 0000
................
0x070000008A7F70F8 : 0000 0000 0000 0000 0000 0000 0000 0000
................
0x070000008A7F7108 : 0000 0000 0000 0000 0000 0000 0000 0000
................
0x070000008A7F7118 : 0000 0000 0000 0000 0000 0100 0000 0000
................
0x070000008A7F7128 : 0000 0000 0000 0000 0000 0000 0000 0000
................
0x070000008A7F7138 : 0000 0000 0000 0000 0000 0000 0000 0000
................ |
