home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Neueste VersionenFixList
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
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IC84527 Status: Geschlossen

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

Produkt:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problembeschreibung:
ADMIN_COPY_SCHEMA utility is not able to copy the given schema 
to other schema. The database instance is using 819 codepage.
Problem-Zusammenfassung:
**************************************************************** 
* 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
verfügbare FixPacks:
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

Lösung
Workaround
export LANG=Ja_JP on server
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
14.06.2012
21.11.2012
21.11.2012
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.1.0.1 FixList
10.5.0.1 FixList