DB2 - Problem description
Problem IC81714 | 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 / 970 - 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 who use graphic column on unicode database. * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to Version 9.7 FixPack 6. * **************************************************************** | |
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 9.7 Fix Pack 6 for Linux, UNIX, and Windows | |
Solution | |
Problem was first fixed in DB2 UDB Version 9.7 FixPack 6. | |
Workaround | |
not known / see Local fix | |
BUG-Tracking | |
forerunner : APAR is sysrouted TO one or more of the following: IC84467 follow-up : | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 29.02.2012 04.06.2012 04.06.2012 |
Problem solved at the following versions (IBM BugInfos) | |
9.7.FP6 | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.7.0.6 |