|
Problem IC82622
|
Status: Geschlossen |
ACTIVITYMETRICS TABLE IS MISSING THE ACTIVATE_TIMESTAMP COLUMN |
| Produkt: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problembeschreibung: |
Starting with Version 9.7 Fix Pack 4, activity metrics are now
reported individually by the activity event monitor in the new
event_activitymetrics logical data group and can now be
collected in a relational table. The relational table used to
hold activitymetrics data is missing the ACTIVATE_TIMESTAMP
column. |
| Problem-Zusammenfassung: |
****************************************************************
* USERS AFFECTED: *
* Anybody using the new activitmetrics table of the activities *
* event monitor *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to Version 9.7 Fix Pack 7. Once the upgrade is *
* complete the activitymetrics table of an existing activities *
* event monitor can be altered to add the activate_timestamp *
* column and then reorganized to make the table usable. For *
* example, if an activities event monitor named "act" was *
* created in v9.7 Fix Pack 6 and uses an activitymetrics table *
* named "activitymetrics_act", the following commands could be *
* used: *
* *
* db2 alter table activitymetrics_act add activate_timestamp *
* timestamp not null with default *
* db2 reorg table activitymetrics_act *
* *
* Otherwise the event monitor can be dropped and recreated to *
* pick up the change. *
**************************************************************** |
| Local-Fix: |
|
| verfügbare FixPacks: |
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 7 |
| Workaround |
keiner bekannt / siehe Local-Fix |
| Bug-Verfolgung |
Vorgänger : APAR is sysrouted TO one or more of the following: IC83252
Nachfolger : |
| Weitere Daten |
Datum - Problem gemeldet :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
| 11.04.2012
09.10.2012
09.10.2012 |
| Problem behoben ab folgender Versionen (IBM BugInfos) |
9.7.FP6,
9.7.FP7
|
| Problem behoben lt. FixList in der Version |
| 9.7.0.7
|
 |
