|
Problem IT04956
|
Status: Closed |
LOAD UTILITY MAY PUT 0X0D CHARACTER AT THE END OF DATA |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
When the load utility with del option is executed from DB2
Client on Windows and the data is stored to the DB2 Server on
Unix, character type data put into a column could be tailed with
0x0D.
On Windows, 0x0D is CR control character and the data in del
format could have 0x0D at end of the lines as 0x0D0A
regularly.
With the combination of DB2 Client on Windows and DB2 Server on
Unix, the character type data loaded by load utility on Windows
may put with 0x0D incorrectly to DB2 Server on Unix.
Note that 0x0d is inserted by load utility executed in DB2
Client or Server on Unix if the input del type data has 0x0d.
This situation could happen when the del type data is created on
Windows and the data is loaded from DB2 on Unix. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* User executing load utility in DB2 Client on Windows *
* platform connecting to DB2 Server on UNIX platform. *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 Version 9.7 Fix Pack 11. *
**************************************************************** |
| Local Fix: |
Convert row delimiters in the data file to server-side format,
i.e. from 0x0D0A to 0x0A, and Load again |
| Solution |
Problem was first fixed in DB2 Version 9.7 Fix Pack 11. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 15.10.2014
13.10.2015
13.10.2015 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP11
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.11
|
 |
