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

%PATH% ENVIRONMENT VARIABLE VALUE IS CHANGED TO LOWER CASE AFTER DB2 IS
INSTALLED ON WINDOWS 7, 2008 R2

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
After installing DB2 v10.1 on certain Windows operating systems 
such as 7 or 2008 R2, the %PATH% environment variable gets 
changed to all lower case and loses any mixed-case values that 
previously existed.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Windows                                                      * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 v10.1 Fixpack 3                               * 
****************************************************************
Local Fix:
Capture the previous %PATH% environment variable value prior to 
installing DB2. After installing DB2, update any of the values 
within the %PATH% that were changed to lower case to the 
previous mixed-case value.
available fix packs:
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 v10.1 Fixpack 3
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
07.03.2013
07.10.2013
07.10.2013
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.3 FixList
10.1.0.3 FixList