|
Problem IC62074
|
Status: Closed |
IMPORT WITH METHOD P MODIFIER MAY PRODUCE SQL3114W TRUNCATION WARNINGS WHEN CHARACTER DELIMITERS EXIST IN DATA. |
| product: |
DB2 FOR LUW / DB2FORLUW / 950 - DB2 |
| Problem description: |
When the Import utility is invoked using the METHOD P modifier,
in some scenarios it is possible for a SQL3114W truncation
warning message to occur, which may incorrectly truncate your
column value. This is due to some problems with double character
delimiter recognition logic. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* All. *
****************************************************************
* PROBLEM DESCRIPTION: *
* When the Import utility is invoked using the METHOD *
* Pmodifier,in some scenarios it is possible for a SQL3114W *
* truncationwarning message to occur, which may incorrectly *
* truncateyourcolumn value. This is due to some problems with *
* doublecharacterdelimiter recognition logic. *
****************************************************************
* RECOMMENDATION: *
* Update to version 9.5 fix pack 6 or later. *
**************************************************************** |
| Local Fix: |
Do not use the METHOD P option and instead re-arrange the
contents of the data file to compensate. |
| available fix packs: |
DB2 Version 9.5 Fix Pack 6a for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
This problem is first fixed in version 9.5 fix pack 6. |
| Workaround |
not known / see Local fix |
| BUG-Tracking |
forerunner : APAR is sysrouted TO one or more of the following: IC66425 IC66426
follow-up : |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 16.07.2009
25.05.2010
25.05.2010 |
| Problem solved at the following versions (IBM BugInfos) |
9.5.FP6
|
| Problem solved according to the fixlist(s) of the following version(s) |
