|
Problem IC84467
|
Status: Closed |
WHEN IMPORT FROM FILE ENCODED IN UTF-8 INTO COLUMN DEFINED AS GRAPHIC ON UNICODE DATABASE, STRING MAY BE TRUNCATED. |
| product: |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 |
| Problem description: |
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. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* All *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to Version 10.1 FixPack 1 *
**************************************************************** |
| Local Fix: |
Use the file type modifier "nochecklengths", if it is known that
the source data will fit in all cases despite mismatched column
definitions. |
| 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 |
Problem was first fixed in DB2 UDB Version 10.1 FixPack 1 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 14.06.2012
01.11.2012
01.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
|
 |
| 10.5.0.1
|
|
