home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Neueste VersionenFixList
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IC83252 Status: Geschlossen

ACTIVITYMETRICS TABLE IS MISSING THE ACTIVATE_TIMESTAMP COLUMN

Produkt:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problembeschreibung:
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-Zusammenfassung:
**************************************************************** 
* 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:
verfügbare FixPacks:
DB2 Version 10.1 Fix Pack 1 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows

Lösung
Problem was first fixed in Version 10.1 Fix Pack 1
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
09.05.2012
31.10.2012
31.10.2012
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.1.0.1 FixList
10.5.0.1 FixList