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

ADMIN_COPY_SCHEMA IS NOT WORKING WITH SJIS DATABASE IF THE INSTANCE IS
STARTED WITH 819 CODEPAGE

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
ADMIN_COPY_SCHEMA utility is not able to copy the given schema 
to other schema. The database instance is using 819 codepage.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Users prior to DB2 V10 FP1                                   * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* ADMIN_COPY_SCHEMA IS NOT WORKING WITH SJIS DATABASE IF THE   * 
* INSTANCE IS STARTED WITH 819 CODEPAGE                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Move to DB2 V10 FP1                                          * 
****************************************************************
Local Fix:
export LANG=Ja_JP on server
available fix packs:
DB2 Version 10.1 Fix Pack 1 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows
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
Workaround
export LANG=Ja_JP on server
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
14.06.2012
21.11.2012
21.11.2012
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.1 FixList
10.5.0.1 FixList