|
Problem IC67009
|
Status: Geschlossen |
DEADLOCK MONITOR ELEMENT MAY NOT GET UPDATED IN APPLICATION SNAPSHOT. |
| Produkt: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problembeschreibung: |
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-Zusammenfassung: |
****************************************************************
* USERS AFFECTED: *
* All platform. *
****************************************************************
* 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 *
****************************************************************
* RECOMMENDATION: *
* Upgrade to V9.7 FP2. *
**************************************************************** |
| Local-Fix: |
|
| verfügbare FixPacks: |
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
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 9a 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 10 for Linux, UNIX, and Windows
|
| Lösung |
DB2 V9.7 FP2 will contain the fix. |
| Workaround |
keiner bekannt / siehe Local-Fix |
| Bug-Verfolgung |
Vorgänger : APAR is sysrouted TO one or more of the following: IC67131
Nachfolger : |
| Weitere Daten |
Datum - Problem gemeldet :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
| 09.03.2010
08.04.2010
08.04.2010 |
| Problem behoben ab folgender Versionen (IBM BugInfos) |
9.7.FP2
|
| Problem behoben lt. FixList in der Version |
| 9.7.0.2
|
 |
