|
Problem IC77676
|
Status: Geschlossen |
ACTIVITIES EVENT MONITOR CORRECTLY RECORDS ONLY THE FIRST REOPT DATA VALUE; ANY OTHER REOPT VALUE RESHOWS THE FIRST VALUE |
| Produkt: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problembeschreibung: |
When an activities event monitor is active and activity with
details and values collection is enabled, any activity that has
been subject to reoptimization and has more than one data value
will correctly records only the first reoptimized data value.
For any other reoptimized data value the first data value is
shown again rather than the correct value. |
| Problem-Zusammenfassung: |
****************************************************************
* USERS AFFECTED: *
* Anybody using the activities event monitor and REOPT *
****************************************************************
* PROBLEM DESCRIPTION: *
* If an activity has been re-optimized and has more than one *
* data value, the first reopt data value is properly recorded. *
* The second data value and any other will report the first *
* value's information. *
****************************************************************
* RECOMMENDATION: *
* Upgrade to Version 9.7 Fix Pack 5 *
**************************************************************** |
| Local-Fix: |
db2pd db <dbName> -reopt will correctly show all the reopt data
values. |
| verfügbare FixPacks: |
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 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
|
| Lösung |
Problem was first fixed in Version 9.7 Fix Pack 5 |
| Workaround |
keiner bekannt / siehe Local-Fix |
| Weitere Daten |
Datum - Problem gemeldet :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
| 22.07.2011
21.12.2011
21.12.2011 |
| Problem behoben ab folgender Versionen (IBM BugInfos) |
9.7.FP5
|
| Problem behoben lt. FixList in der Version |
| 9.7.0.5
|
 |
