DB2 FOR LUW / DB2FORLUW / 970 - DB2

If a column is defined as GRAPHIC(n), and when importing the 
data in "n" characters in a file encoded in UTF-8, the 
characters may be truncated, since the character strings in 
UTF-8 format may have different lengths in bytes from the target 
column. 
However, as long as the same number of characters is defined, it 
should be imported.

**************************************************************** 
* USERS AFFECTED:                                              * 
* All who use graphic column on unicode database.              * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to Version 9.7 FixPack 6.                            * 
****************************************************************

Use the file type modifier "nochecklengths", if it is known that 
the source data will fit in all cases despite mismatched column 
definitions.

DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
 DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
 

Problem was first fixed in DB2 UDB Version 9.7 FixPack 6.

keiner bekannt / siehe Local-Fix

Vorgänger  : APAR is sysrouted TO one or more of the following: IC84467 
Nachfolger : 

Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:

29.02.2012
04.06.2012
04.06.2012

9.7.FP6