DB2 - Problem description
Problem IT21834 | Status: Closed |
DB2MOVE MAY NOT COPY UNDER SUPPORTED MULTI-BYTE CODE CONVERSION ENVIRONMENT | |
product: | |
DB2 FOR LUW / DB2FORLUW / B10 - DB2 | |
Problem description: | |
Here is an example test case. ----- repro.sh ----- #!/bin/sh export LANG=Ja_JP db2 drop db db1 db2 drop db db2 db2 create db db1 using codeset UTF-8 territory JP db2 create db db2 using codeset UTF-8 territory JP db2 connect to db1 db2 -tv "CREATE TABLESPACE SYSTOOLSPACE IN IBMCATGROUP MANAGED BY AUTOMATIC STORAGE USING STOGROUP IBMSTOGROUP EXTENTSIZE 4" db2 -v "create table AAA (col1 int, col2 int)" # Table name "AAA" is valid multi-byte three Ja_JP characters db2 terminate db2 connect to db2 db2 -tv "CREATE TABLESPACE SYSTOOLSPACE IN IBMCATGROUP MANAGED BY AUTOMATIC STORAGE USING STOGROUP IBMSTOGROUP EXTENTSIZE 4" db2 terminate db2move DB1 COPY -sn $USER -co target_db DB2 NONRECOVERABLE -u db2inst1 -p password ----- db2move fails with SQLCODE = -204 in COPYSCHEMA.xxxx.ERR This can be occurred when database codeset and LANG is not same locale as above example. If export LANG=JA_JP.UTF8 which is the same locale of database codeset UTF-8 in the above example, the problem does not occur. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * Db2 Version 11.1 * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to Db2 Version 11.1 Mod 2 Fix Pack 2. * **************************************************************** | |
Local Fix: | |
Set the same database codeset to LANG | |
Solution | |
Workaround | |
not known / see Local fix | |
BUG-Tracking | |
forerunner : IT16881 follow-up : | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 04.08.2017 10.10.2017 10.10.2017 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) |