|
Problem IC89200
|
Status: Closed |
COLUMN CONTAINING INVALID CHARACTER DATA REJECTED BY LOAD REMOTE FETCH |
| product: |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 |
| Problem description: |
If a column contains invalid character data (leftover/dangling
bytes which cannot be converted properly at the end of column
data), so that Load Remote Fetch rejects the row. However, Load
from Nickname for the same table and data accepts the row.
This APAR will fix Load Remote Fetch to replace such invalid
bytes with substitution character and then accept the row. After
that, Load Remote Fetch and Load from Nickname would have
consistent behaviors. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* Users using Load Remote Fetch on DB2 for LUW V10.1 Fixpack 2 *
* and lower. *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 for LUW Version 10.1 Fixpack 3 or higher. *
**************************************************************** |
| Local Fix: |
|
| available fix packs: |
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 |
First fixed in DB2 for LUW Version 10.1 Fixpack 3. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 19.12.2012
07.10.2013
07.10.2013 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.1.0.3
|
 |
| 10.1.0.3
|
|
