topic Re: ECC5 DB export in Application Development and Automation Discussions

ECC5 DB export

Former Member — Thu, 09 Dec 2010 12:49:21 GMT

We are performing a Unicode upgrade on an ECC 5.0 system. The ECC 5.0

is a MDMP System. After completing Unicode preparatory activities, we

have started to perform a system export using SAPINST.

We have used table splitting option to speed the export process, export

was running and now it has stopped with an error. On analyzing the log

files we observed the following error.

ERROR: file /exportts6/exp/ACCTHD~2.TSK.bck already seems to exist

a previous run may not have been finished cleanly

file /exportts6/exp/ACCTHD~2.TSK possibly corrupted

Also, we notice many *.bck files existing in the system. However, the

relavent TST files for .BCK files does not exist in the system.

Kindly help us resolve the problem at the earliest.

Thanks

Vinay

Re: ECC5 DB export

markus_doehr2 — Fri, 10 Dec 2010 12:41:44 GMT

either

- add "-merge_bck" in the export_monitor_cmd.properties files and restart the export or

- execute "R3load -merge_only" for each of the TSK files.

Markus

Re: ECC5 DB export

Former Member — Fri, 10 Dec 2010 12:58:59 GMT

Hello Markus,

Thanks for your response.

export_monitor_cmd.properties not found in the log files and for all bck files there is no TSK files exist(starnge).

We faced export file system full during export, so we are suspecting that incident will be the cause for the issue.

We are using SAPINST 640 for exporting ECC5 system, in this we are proceeding wit R3load copy method.

Regards

Vinay

Re: ECC5 DB export

markus_doehr2 — Fri, 10 Dec 2010 13:03:10 GMT

> export_monitor_cmd.properties not found in the log files and for all bck files there is no TSK files exist(starnge).

So you're not using the migration monitor... I'd use that one for big exports, much more convenient than sapinst (sapinst uses it too but you can configure it better if you use it directly).

> We faced export file system full during export, so we are suspecting that incident will be the cause for the issue.

> We are using SAPINST 640 for exporting ECC5 system, in this we are proceeding wit R3load copy method.

I understood what you're saying .

So if the .TSK files are not there you are missing tables - you'll have to start over with the export.

Markus

Re: ECC5 DB export

Former Member — Sat, 11 Dec 2010 09:19:24 GMT

Hello,

I have started fresh export.

Regards

Vinay