|
Problem IC67131
|
Status: Closed |
DEADLOCK MONITOR ELEMENT MAY NOT GET UPDATED IN APPLICATION SNAPSHOT. |
| product: |
DB2 FOR LUW / DB2FORLUW / 980 - DB2 |
| Problem description: |
deadlock monitor element in application snapshot may not get
updated when deadlock happen.
From the application snapshot output, the "Internal rollbacks
due
to deadlock" element is more that 1 but the "Deadlocks detected"
element is still 0.
Lock timeout (seconds) = -1
Locks held by application = 0
Lock waits since connect = 1
Time application waited on locks (ms) = 7272
Deadlocks detected = 0
Lock escalations = 0
Exclusive lock escalations = 0
Number of Lock Timeouts since connected = 0
....
Internal automatic rebinds = 0
Internal rows deleted = 0
Internal rows inserted = 0
Internal rows updated = 0
Internal commits = 1
Internal rollbacks = 1
Internal rollbacks due to deadlock = 1 |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* All platform *
****************************************************************
* PROBLEM DESCRIPTION: *
* see APAR description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to V9.8 FP3 *
**************************************************************** |
| Local Fix: |
|
| available fix packs: |
DB2 Version 9.8 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.8 Fix Pack 4 for AIX and Linux
DB2 Version 9.8 Fix Pack 5 for AIX and Linux
|
| Solution |
Fix in V9.8 FP3. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 11.03.2010
20.12.2010
20.12.2010 |
| Problem solved at the following versions (IBM BugInfos) |
9.8.FP3
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.8.0.3
|
 |
