|
Problem IC81498
|
Status: Closed |
LOCKWAIT EVENT CAN INCORRECTLY GET RECORDED AS A DEADLOCK EVENT IN NOTIFY LOG. |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
Lockwait events can incorrectly get recorded as deadlock events
in the administration notify log. For example,
2012-02-08-11.15.55.904555 Instance:e97q5a Node:000
PID:15335692(db2agent (SAMPLE) 0) TID:8824
Appid:*LOCAL.e97q5a.120208021554
database monitor sqmLockEvents::collectLockEvent Probe:274
Database:SAMPLE
ADM5506I "Deadlock" event has occurred on lock
"00030005000000000000000652" at
timestamp "2012-02-08-11.15.55.903720" with event ID "1". The
affected
application is named "db2bp", and is associated with the
workload name
"SYSDEFAULTUSERWORKLOAD" and application ID
"*LOCAL.e97q5a.120208021539" at
member "0". The role that this application plays with respect to
this lock is:
"Participant".
However, the corresponding value from the EVENT_TYPE column
(from the event monitor table) does not match ADM55061I.
db2 "select unique EVENT_TYPE,EVENT_TIMESTAMP from LOCKEVMON
where event_type='LOCKWAIT'"
EVENT_TYPE EVENT_TIMESTAMP
-------------------------------- --------------------------
LOCKWAIT 2012-02-08-11.15.55.903720
where,
LOCKEVMON was generated using the following command
CREATE EVENT MONITOR LOCKEVMON FOR LOCKING WRITE TO UNFORMATTED
EVENT TABLE
In the output above, the event with the given timestamp was of
Lockwait type, but it got recorded in the notify log as of
Deadlock
type.
Lockwait events are not recorded in the notification log. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* Lockwait events can incorrectly get recorded as deadlock *
* events in the administration notify log. For example, *
* *
* 2012-02-08-11.15.55.904555 Instance:e97q5a Node:000 *
* PID:15335692(db2agent (SAMPLE) 0) TID:8824 *
* Appid:*LOCAL.e97q5a.120208021554 *
* database monitor sqmLockEvents::collectLockEvent Probe:274 *
* Database:SAMPLE *
* *
* ADM5506I "Deadlock" event has occurred on lock *
* "00030005000000000000000652" at timestamp *
* "2012-02-08-11.15.55.903720" with event ID "1". *
* The affected application is named "db2bp", and is associated *
* with the workload name *
* "SYSDEFAULTUSERWORKLOAD" and application ID *
* "*LOCAL.e97q5a.120208021539" at member "0". The role that *
* this application plays with respect to this lock is: *
* "Participant". *
* *
* However, the corresponding value from the EVENT_TYPE column *
* (from the event monitor table) does not match ADM55061I. *
* *
* db2 "select unique EVENT_TYPE,EVENT_TIMESTAMP from LOCKEVMON *
* where event_type='LOCKWAIT'" *
* *
* EVENT_TYPE EVENT_TIMESTAMP *
* -------------------------------- -------------------------- *
* LOCKWAIT 2012-02-08-11.15.55.903720 *
* *
* where, *
* LOCKEVMON was generated using the following command *
* CREATE EVENT MONITOR LOCKEVMON FOR LOCKING WRITE TO *
* UNFORMATTED *
* EVENT TABLE *
* *
* In the output above, the event with the given timestamp was *
* of *
* Lockwait type, but it got recorded in the notify log as of *
* Deadlock *
* type. *
* Lockwait events are not recorded in the notification log. *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 UDB version 9.7 fixpack 6. *
**************************************************************** |
| Local Fix: |
|
| available fix packs: |
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
|
| Solution |
Problem was first fixed in DB2 UDB Version 9.7 FixPack 6. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 16.02.2012
18.06.2012
18.06.2012 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP6
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.6
|
 |
