|
Problem IC85428
|
Status: Closed |
LOCK NAMES RECORDED BY DEADLOCK EVENT MONITOR ARE NOT CORRECT |
| product: |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 |
| Problem description: |
The DEADLOCK WITH DETAILS event monitor (including
db2detaildeadlock) does not properly record the lock name for
any deadlock participant. This makes deadlock analysis very
difficult since none of the involved locks can be ascertained.
This affects serial, dpf and pureScale instances.
For example, running db2evmon against a deadlock recorded by the
db2detaildeadlock event monitor shows the lock names as hex
zeros:
5) Deadlock Event ...
Deadlock ID: 1
Number of applications deadlocked: 2
Deadlock detection time: 07/19/2012 09:58:00.035123
Rolled back Appl participant no: 2
Rolled back Appl Id: *LOCAL.jwr.120719135757
Rolled back Appl seq number: 00001
Rolled back Appl handle: 41
6) Connection Header Event ...
Appl Handle: 41
Appl Id: *LOCAL.jwr.120719135757
Appl Seq number: 00001
DRDA AS Correlation Token: *LOCAL.jwr.120719135757
Program Name : db2bp
Authorization Id: JWR
Execution Id : jwr
Codepage Id: 819
Territory code: 1
Client Process Id: 29229228
Client Database Alias: SAMPLE
Client Product Id: SQL10011
Client Platform: AIX 64BIT
Client Communication Protocol: Local
Client Network Name: hotelaix12
Connect timestamp: 07/19/2012 09:57:53.208599
7) Deadlocked Connection ...
Deadlock ID: 1
Participant no.: 2
Participant no. holding the lock: 1
Appl Id: *LOCAL.jwr.120719135757
Appl Seq number: 00001
Appl Id of connection holding the lock:
*LOCAL.jwr.120719135756
Seq. no. of connection holding the lock: 00001
Lock wait start time: 07/19/2012 09:57:54.806557
Lock Name : 0x00000000000000000000000000
<-----------------------------
Lock Attributes : 0x00000000
Release Flags : 0x00000000
Lock Count : 0
Hold Count : 0
Deadlock detection time: 07/19/2012 09:58:00.035447
Table of lock waited on : ORG
Schema of lock waited on : JWR
Data partition id for table : 0
Tablespace of lock waited on : USERSPACE1
Type of lock: Table
Mode of lock: X - Exclusive
Mode application requested on lock: IS - Intent Share
:
8) Connection Header Event ...
Appl Handle: 40
Appl Id: *LOCAL.jwr.120719135756
Appl Seq number: 00001
DRDA AS Correlation Token: *LOCAL.jwr.120719135756
Program Name : db2bp
Authorization Id: JWR
Execution Id : jwr
Codepage Id: 819
Territory code: 1
Client Process Id: 59637878
Client Database Alias: SAMPLE
Client Product Id: SQL10011
Client Platform: AIX 64BIT
Client Communication Protocol: Local
Client Network Name: hotelaix12
Connect timestamp: 07/19/2012 09:57:53.184332
9) Deadlocked Connection ...
Deadlock ID: 1
Participant no.: 1
Participant no. holding the lock: 2
Appl Id: *LOCAL.jwr.120719135756
Appl Seq number: 00001
Appl Id of connection holding the lock:
*LOCAL.jwr.120719135757
Seq. no. of connection holding the lock: 00001
Lock wait start time: 07/19/2012 09:57:54.806788
Lock Name : 0x00000000000000000000000000
<--------------
Lock Attributes : 0x00000000
Release Flags : 0x00000000
Lock Count : 0
Hold Count : 0
Deadlock detection time: 07/19/2012 09:58:00.036469
Table of lock waited on : STAFF
Schema of lock waited on : JWR
Data partition id for table : 0
Tablespace of lock waited on : USERSPACE1
Type of lock: Table
Mode of lock: X - Exclusive
Mode application requested on lock: IS - Intent Share |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* Anybody using a DEADLOCKS event monitor *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to Version 10.1 Fix Pack 2 *
**************************************************************** |
| Local Fix: |
Use a LOCKING event monitor to obtain the lock names involved in
a deadlock |
| available fix packs: |
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 2 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 19.07.2012
21.12.2012
21.12.2012 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.1.0.2
|
 |
| 10.5.0.2
|
|
