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

DATA TRUNCATION WITHOUT A WARNING MESSAGE WHEN EXPORTING FROM DB2 V8
FOR Z/OS TO DB2 LUW V9.7.

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
Data trancation might happen during export if the codepages ued 
are unsupported. 
For eg : "unicode client to non-unicode server not supported" 
and the truncation event is known in such cases. 
 
Fix includes to give a global (i.e. not per-row) SQL3132W 
warning if a truncation may potentially occur.  This is the 
current behaviour for DB2 LUW that is not working with DB2 
z/OS, and the fix is to make DB2 z/OS work like DB2 LUW. 
 
Receiving a warning means "a truncation may occur with 
that column". 
With the fix, "no warning" will mean "there was no truncation", 
but a warning means "there may or may not be a truncation with 
user's actual data".
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Users using lower versions than V9.7 FP2                     * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* DATA TRUNCATION WITHOUT A WARNING MESSAGE WHEN EXPORTINGFROM * 
* DB2 V8 FOR Z/OS TO DB2 LUW V9.7.                             * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to  DB2 V9.7 FP2                                     * 
****************************************************************
Local Fix:
Users should export data into the same codepage if possible so 
that there will be no codepage conversion issue during export. 
The import/load may need a codepage conversion though.
available fix packs:
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
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 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows

Solution
First fixed in DB2 V9.7 FP2
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
11.02.2010
22.06.2010
22.06.2010
Problem solved at the following versions (IBM BugInfos)
9.7.FP2
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.2 FixList