home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
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 IC62307 Status: Closed

CHANGE THE LOCATION OF PDLOG RELATED DUMP FILES

product:
DB2 CONNECT / DB2CONNCT / 970 - DB2
Problem description:
Change the location of pdLog related dump files to <system app 
data path>\IBM\DB2\DB2COPY name for dsdriver in windows. Also 
the pdLog location for clidriver in Windows should be <system 
app data path>\IBM\DB2\CLIDRIVER\<unzipped path>. 
 
For eg: if the cli driver <unzipped path> is 
 
D:\Program Files\IBM\clidriver 
 
then the pdlog path for cli driver should be 
 
<system app data path>\IBM\DB2\CLIDRIVER\D_Program 
Files_IBM_clidriver 
 
Also since the clidriver can be just unzipped into some path and 
there is no installer to create the path required for pd/related 
dump files, oss has to create the directory if it is not 
existing.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Windows                                                      * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* Currently db2diag.log and related dump files are written to  * 
* the installation directory of Data Server Driver. So users   * 
* need permissions to write to this directory which is a       * 
* violation of Windows security standards.                     * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to IBM Data Server Provider for .Net 9.7 Fix Pack 1  * 
****************************************************************
Local Fix:
available fix packs:
DB2 Version 9.7 Fix Pack 1 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a 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 10 for Linux, UNIX, and Windows

Solution
The location of db2diag.log and dump files is now changed to 
<system app 
data path>\IBM\DB2\DB2COPY name for dsdriver in windows. 
The location for clidriver in Windows should be <system app data 
path>\IBM\DB2\CLIDRIVER\<unzipped path>. 
 
Also when there is no installer to create the path required for 
these files, the directory has to be created if it not exists. 
 
 
 
Problem was first fixed in Version 9.7 Fix Pack 1 
This fix should be applied on the client.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
30.07.2009
04.01.2010
04.01.2010
Problem solved at the following versions (IBM BugInfos)
9.7.FP1
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.1 FixList