Question Re: DB6 : System copy import database with splitted_load in Technology Q&A

DB6 : System copy import database with splitted_load

former_member13267 — Mon, 26 Apr 2021 11:47:21 GMT

Dear all,

is there any online documentation for the fabled ,,splitted_load" option for system import ?

I've been asked by SAP to use that option, they even showed me a note

https://launchpad.support.sap.com/#/notes/1058437

it briefly describes the splitted_load option, but it doesn't give any hints, how to use it properly, the only requirement is that the table is splitted beforehand, and that the table has no indexes yet.
But how can I use it with swpm ? Can that option be used with automatic swpm ?
How can I make swpm import data before creating indexes ?
Best regards,
Peter

Re: DB6 : System copy import database with splitted_load

SabineReich — Mon, 26 Apr 2021 12:47:21 GMT

Hi Peter, the system copy guides are available here, maybe this helps?

System Copy - Target Databases Other than SAP HANA

Kind regards, Sabine

Re: DB6 : System copy import database with splitted_load

former_member13267 — Tue, 27 Apr 2021 10:47:23 GMT

Hi,

I'm well aware of that guide, but thanks for the link 😉

It does not have the proper information sadly.

Peter

Re: DB6 : System copy import database with splitted_load

maria_shen — Wed, 28 Apr 2021 06:49:33 GMT

Hello Peter,

As you know in below thread, the splitted_load is a kind of expert option that is not easy to use with SWPM and Migmon.

VBFA / KOCLU / CDCLS migration

This may require to call the R3load manually, which can not be fully achieved via 'automatic' SWPM.

Thank you.

Kind regards
Maria

Re: DB6 : System copy import database with splitted_load

Frank-Martin — Fri, 30 Apr 2021 08:00:17 GMT

Hi Peter,

I am no SWPM expert but you may not be able to use the R3load option SPLITTED_LOAD with SWPM because of the way SWPM orchestrates R3load with one MigMon instance. When using SPLITTED_LOAD for some tables it needs to be ensured that the first CREATE INDEX step is executed only after all data parts of the table have been loaded (into temporary tables). The first CREATE INDEX statement then triggers the merge of the data from the temporary tables into the target table.

I know that the SPLITTED_LOAD option has been used with success by IBM migration experts. However as far as I know the used scripts to start the R3load processes for the SPLITTED_LOAD tables.

Regards
Frank