DB2 - Problem description
Problem IC76691 | Status: Closed |
V9.1FP10: GUI TOOLS SHOW ALL JAPANESE CHARACTERS AS SQUARES ON RHEL 5. | |
product: | |
DB2 FOR LUW / DB2FORLUW / 910 - DB2 | |
Problem description: | |
The GUI tools include db2setup, Control Center shows all Japanese characters as squares in RHEL 5 Japanese systems. The Java 5 bundled with the fixpacks is not picking up correct fontconfig file on RHRL 5, and it uses default fontconfig file. The default RedHat fontconfig file are updated in v9.1fp10 and v9.5fp7, and updated file is not compatible with RHEL 5. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * Users who use GUI tools in Japanese environment. * **************************************************************** * PROBLEM DESCRIPTION: * * The GUI tools include db2setup, Control Center shows all * * Japanese characters as squares in RHEL 5 Japanese systems. * * The Java 5 bundled with the fixpacks is not picking up * * correct * * fontconfig file on RHRL 5, and it uses default fontconfig * * file. * **************************************************************** * RECOMMENDATION: * * Please upgrade to V9.1 FixPack 11 or later. * **************************************************************** | |
Local Fix: | |
db2setup: Please launch db2setup from English environment. for example: # export LANG=C # db2setup GUI tools: Please override fontconfig.RedHat.bfc by fontconfig.RedHat.5.bfc. for example: # cd sqllib/java/jre/lib # mv fontconfig.RedHat.bfc fontconfig.RedHat.bfc.bk # cp -p fontconfig.RedHat.5.bfc fontconfig.RedHat.bfc | |
available fix packs: | |
DB2 Version 9.1 Fix Pack 11 for Linux, UNIX and Windows | |
Solution | |
This problem is first fixed in DB2 V9.1 FixPack 11. | |
Workaround | |
not known / see Local fix | |
BUG-Tracking | |
forerunner : APAR is sysrouted TO one or more of the following: IC76753 follow-up : | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 31.05.2011 02.01.2012 02.01.2012 |
Problem solved at the following versions (IBM BugInfos) | |
9.1.FP11 | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.1.0.11 |