|
Problem IC79818
|
Status: Closed |
DB2 INSTALLATIONS UNDER CHINESE, KOREAN OR JAPANESE LANGUAGES RESULT IN MISALIGNED TEXT IN THE LOG FILE |
| product: |
DB2 FOR LUW / DB2FORLUW / 950 - DB2 |
| Problem description: |
After an installation of DB2, the log file contains
misaligned text for Chinese, Korean or Japanese. Moreover, the
same
phenomenon exists on the GUI installation summary panel as well.
The misalignment can be found after these strings:
Target Directory:
Space Required:
Install SA MP Base Component:
How to reproduce the problem:
i) Change the language to Simplified Chinese.
#export LANG=zh_CN
ii) Navigate to DB2 install package and run ./db2_install -p
ese or launch DB2 Setup wizard using db2setup
iii) The db2 setup log file will contain misaligned text. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* NONE *
****************************************************************
* PROBLEM DESCRIPTION: *
* After a silent install of ESE, the output log file contains *
* misaligned texts in National Languages. Moreover, the same *
* phenomenon exists on the GUI installation summary panel as *
* well. *
* *
* Misalignment can be found after these strings: 'Target *
* Directory: ', 'Space Required: ', and 'Install SA MP Base *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 v9.5 Fixpack 9 or above *
**************************************************************** |
| Local Fix: |
N/A |
| available fix packs: |
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
The misaligned texts in output log file and GUI install panel
should be aligned. |
| Workaround |
not known / see Local fix |
| BUG-Tracking |
forerunner : APAR is sysrouted TO one or more of the following: IC79929 IC84152
follow-up : |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 15.11.2011
07.03.2012
07.03.2012 |
| Problem solved at the following versions (IBM BugInfos) |
9.5.FP9
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.5.0.9
|
 |
