Latest versionsfixlist
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
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IC86852 Status: Closed

CHANGE HISTORY EVENT MONITOR SHOWS INCORRECT EVENT_TYPE VALUE FOR THE
UTILLOCATION LOGICAL DATA GROUP

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
The UTILLOCATION logical data group is produced by the change 
history event monitor.  Each UTILLOCATION row shows a file or 
path that is associated with the start of a utility.  The 
EVENT_TYPE element incorrectly shows the value UTILLOCATION 
rather than UTILSTART.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Anyone using change history event monitor with utillocation  * 
* logical group                                                * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to Version 10.1 Fix Pack 2                           * 
****************************************************************
Local Fix:
available fix packs:
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

Solution
Problem was first fixed in Version 10.1 Fix Pack 2
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
26.09.2012
07.11.2012
07.11.2012
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.2 FixList
10.5.0.2 FixList