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 IC87841 Status: Closed

IF DIR FOR STATISTIC EVENT LOG WAS CHANGED TO DIR DIFFERENT FROM DEFAULT,
PD_GET_DIAG_HIST CANNOT RECOGNIZE NEW DIR.

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
The default directory for statistic event logs is 
DIAGPATH/events/ ( e.g.: /home/user1/sqllib/db2dump/events/ ). 
User can change this default directory to a different one, for 
example: 
 
db2set DB2_OPTSTATS_LOG=ON, DIR=/home/user1/temp/ 
 
Then, PD_GET_DIAG_HIST against OPTSTATS still goes to default 
directory to retrieve data, instead of the new directory to 
retrieve data.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to 10.1 FP2 or subsequent fix pack                   * 
****************************************************************
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
First Fixed In DB2 Version 10.1 Fix Pack 2
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
04.11.2012
17.01.2013
17.01.2013
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