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

LOAD FROM CURSOR USING REMOTE FETCH AND MODIFIED BY CODEPAGE DOES NOT
RETURN ERROR

product:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problem description:
Load from remote cursor does not support modified by codpage. 
However no error is returned. 
 
Sample of the issue. 
 
db2 LOAD FROM CUR13414 OF CURSOR MODIFIED BY codepage=1208 
REPLACE  INTO RMPP001.TEST_CUST NONRECOVERABLE 
db2 LOAD FROM CUR13414 OF CURSOR MODIFIED BY codepage=819 
REPLACE  INTO RMPP001.TEST_CUST NONRECOVERABLE 
 
It did not work , still put the same data . 
 
            12186836 575256008           MU¹OZ ROJAS CUE 
 
Customer exported the data , scp it over to Linux and run the 
import or load with code page 1208 it works 
 
db2 "load from ./AIX1.del of del modified by codepage=1208 
insert into rmpp001.test_cust" 
db2 "import from ./AIX1.del of del insert into 
rmpp001.test_cust" 
 
12186836 575256008           MU¹OZ ROJAS
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All Users                                                    * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to the latest release.                               * 
****************************************************************
Local Fix:
Perform a export and import of the data.
Solution
First fixed in V10.5 fix pack 7.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
26.03.2015
25.01.2016
25.01.2016
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.5.0.7 FixList