DB2 - Problem description
Problem IC83252 | Status: Closed |
ACTIVITYMETRICS TABLE IS MISSING THE ACTIVATE_TIMESTAMP COLUMN | |
product: | |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 | |
Problem description: | |
In Version 10.1 activity metrics are reported individually by the activity event monitor in the event_activitymetrics logical data group (in addition to appearing in the XML document in the details_xml column of the event_activity 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 Summary: | |
**************************************************************** * USERS AFFECTED: * * Anybody using the new activitmetrics table of the activities * * event monitor * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to Version 10.1 Fix Pack 1. Once the upgrade is * * complete run the evmon_upgrade_tables procedure to ensure * * the activitymetrics table of any existing activities event * * monitor has been 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 v10.1 GA and uses an activitymetrics table named * * "activitymetrics_act", the following command could be used: * * * * db2 "call evmon_upgrade_tables('ACT', null, null, ?, ?, ?)" * * * * Please read any usage notes concerning evmon_upgrade_tables * * before running the procedure. * **************************************************************** | |
Local Fix: | |
available fix packs: | |
DB2 Version 10.1 Fix Pack 1 for Linux, UNIX, and Windows | |
Solution | |
Problem was first fixed in Version 10.1 Fix Pack 1 | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 09.05.2012 31.10.2012 31.10.2012 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) | |
10.1.0.1 | |
10.5.0.1 |