Smooth way to restart failed R3loads with table splitting

[Former Member]

Hi,

We are running a Unicode conversion with largest tables split into 10 or more export/import packages.

Now some of the packages fail, as they normally do.

We use sockets technique.

Do you find a smooth and reliable way to

- delete already imported rows using where clause from the TSK files (both export and import servers)

- replace "err" with "xeq" (or something else?) in TSK file (both export and import servers)

- replace "=-" with "=0" in export_state.properties and import_state.properties

?

We have done this manually with vi editor, but to me it sounds a bit too risky, as migration monitor itself might be trying to modify contents of .properties files simultaneously.

We are looking for best practices on this one. All you techies, share your experience!

Thanks a lot!

BR.

Samuli Kaisanlahti

Certified Netweaver Basis consultant

[Former Member]

Dear Samuli,

My experience with R3load is that editing and modifying TSK files could lead to problems and inconsistences, that will probably appear weeks after the import.

I'd recommend that, in case of problems, you start the complete load from scratch.

Regards

Francisco