System copy - DB export error

[Former Member]

Dear all,

I run an heterogeneous system copy with R3load method.

The source system is ECC5.0 Unicode on HP-UX(codepage 4102).

The target system is ECC5.0 Unicdoe on SUSE10(codepage 4103).

During parameter setting of DB export phase, i set the datafile codepage "4103".

But when export table DYNPSOURCE, it occur error with following message :

/sapmnt/JCP/exe/R3load: START OF LOG: 20091214020151

/sapmnt/JCP/exe/R3load: sccsid @(#) $Id: //bas/640_REL/src/R3ld/R3load/R3ldmain.c#27 $ SAP

/sapmnt/JCP/exe/R3load: version R6.40/V1.4 [UNICODE]

Compiled Oct 10 2009 10:27:36

/sapmnt/JCP/exe/R3load -datacodepage 4103 -e /sapback/tmp/sapinst_instdir/ECC50/COPY/EXPORT/ABAP/COPY/UC/DBEXP

/SAPXXX75.cmd -l /sapback/tmp/sapinst_instdir/ECC50/COPY/EXPORT/ABAP/COPY/UC/DBEXP/SAPXXX75.log

-stop_on_error

(DB) INFO: connected to DB

(DB) INFO: DbSlControl(DBSL_CMD_NLS_CHARACTERSET_GET): UTF8

(DB) INFO: Export without hintfile

(GSI) INFO: dbname = "JCP20060425030449 "

(GSI) INFO: vname = "ORACLE "

(GSI) INFO: hostname = "SAP-PRD "

(GSI) INFO: sysname = "HP-UX"

(GSI) INFO: nodename = "SAP-PRD"

(GSI) INFO: release = "B.11.23"

(GSI) INFO: version = "U"

(GSI) INFO: machine = "ia64"

(GSI) INFO: instno = "0020234983"

(DBC) Info: No commits during lob export

Error 2 during decompression

PROGNAME 00 52 00 50 00 4c 00 50 00 4b 00 4b 00 43 00 30 |.R.P.L.P.K.K.C.0|

PROGNAME 00 20 00 20 00 20 00 20 00 20 00 20 00 20 00 20 |. . . . . . . . |

PROGNAME 00 20 00 20 00 20 00 20 00 20 00 20 00 20 00 20 |. . . . . . . . |

PROGNAME 00 20 00 20 00 20 00 20 00 20 00 20 00 20 00 20 |. . . . . . . . |

PROGNAME 00 20 00 20 00 20 00 20 00 20 00 20 00 20 00 20 |. . . . . . . . |

DYNPNUMBER 00 31 00 30 00 30 00 30 |.1.0.0.0 |

R3STATE 00 41 |.A |

(CNV) ERROR: data conversion failed. rc = 2

(DB) INFO: disconnected from DB

/sapmnt/JCP/exe/R3load: job finished with 1 error(s)

/sapmnt/JCP/exe/R3load: END OF LOG: 20091214023617

Then I check the TSK files and all of other tables are export successfully.

Can anyone help me with this?

Thanks in advance,

Best Regards,

Wu

[former_member720526]

Can you check in the source system to see if this is table is the largest or one of the largest tables in the database? This could be the case if this system was migrated to unicode. If so, try the splitting option.

You might also want to make sure the export file is not reaching the hard limit of the filesize at the OS level.

regards

Vipin

[Former Member]

Hi Vipin,

I check the table and it is small (300MB, the largest table size is 21GB).

And during DB export, i had already set the data file size to 1GB, so it doesn't reach the hard limit of the filesize at the OS level.

Best Regards,

Sean

[Former Member]

Dear Wu,

Are you using the latest R3load for the export ?. If Not perform the export with the Latest r3load.

Gerard

[Former Member]

Hi Gerard,

Before running system copy, i upgrade the kernel to the newest one.

BR.

Sean

[former_member235680]

Hi,

Could you please check that do u have any *.STR files in the export directory?

Thanks

Abhishek

[Former Member]

Hi Abhishek,

Yes, there are many *.STR in the export directory.

According to the *.TSK, all of tables except DYNPSOURCE are export succssfully.

Best Regards,

Wu