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

DB2IUPGRADE FAILS WHEN SYSTEM LANG DOES NOT MATCH DB2 INSTALLED LANG

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
The DB2 install was done with an en_US locale. 
The local server has a locale set in the control panel that is 
something other than en_US. 
 
In the Windows environment, the db2iupgrade executable reads the 
locale information from the OS first if the instance is down. 
This is then used to tell db2ckupgrade where to look for the 
messages file that goes with it.  Then when db2iupgrade starts 
db2ckupgrade it uses a fully qualified directory location for 
the messages file that reflects the server's locale and not 
where the DB2 install has put it. This makes db2ckupgrade fail 
when it cannot find the messages file and thus db2iupgrade 
fails. 
 
So, for db2iupgrade to construct the path to the messages file 
correctly it must use the LANG of the DB2 install and not the 
LANG of the system which could be different from the DB2 
Install.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Windows                                                      * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 V9.7 Fixpak 8                                 * 
****************************************************************
Local Fix:
When the server's locale is changed to the US locale then 
db2iupgrade and db2ckupgrade are able to find the 
correct messages file and the upgrade succeeds.  Once the 
upgrade is successful then the server's locale can be reverted 
back to the original locale setting. Another workaround is to 
set DB2LANG=en_US in the environment.
available fix packs:
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 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows

Solution
First fixed in DB2 V9.7 Fixpak 8
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
29.08.2012
06.05.2013
06.05.2013
Problem solved at the following versions (IBM BugInfos)
9.7.
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.8 FixList