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

SQL0332N AFTER ALTERING COLUMN LENGTH

product:
DB2 FOR LUW / DB2FORLUW / B10 - DB2
Problem description:
When we use mixed codepage(such as 1363), altering column length 
returns SQL0332N. 
This happens because new value is regarded as single byte 
codepage, instead of mixed codepage. 
Please check the repro script and result like as follows. 
------------------------------------------- 
$ db2 create db test_db using codeset 1363 territory kr 
DB20000I  The CREATE DATABASE command completed successfully. 
$ db2 connect to test_db 
 
   Database Connection Information 
 
 Database server        = DB2/SUN64 10.5.9 
 SQL authorization ID   = DBGUEST1 
 Local database alias   = TEST_DB 
 
$ db2 "create table instv.tsmacpt12 (???????? char(6) NOT NULL)" 
DB20000I  The SQL command completed successfully. 
$ db2 "insert into instv.tsmacpt12 values 'test12'" 
DB20000I  The SQL command completed successfully. 
$ db2 "alter table instv.tsmacpt12 alter column "????????" set 
data type char(10)" 
DB20000I  The SQL command completed successfully. 
$ db2 "select * from instv.tsmacpt12" 
 
???????? 
------------------------ 
SQL0332N  Character conversion from the source code page "1363" 
to the target 
code page "1126" is not supported.  SQLSTATE=57017
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to Db2 11.1 Fixpack 3 Mod 2 or higher                * 
****************************************************************
Local Fix:
Solution
First fixed in Db2 11.1 Fixpack 3 Mod 2
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
04.05.2018
07.08.2018
07.08.2018
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)