thank you Regan.
you continuously giving my feedback. I have test this option earlier in my SAP ECC 6 MAXDB 7.7.06. but it take very long time and did not create WHR file.
I read one forum from andres Herzaon as below. he says to create table at OS level via R3ta. do you have any idea what he saying. if i understand how to create R3ta table splitting. but you can guide me the sequence. and further one thing how i can run sapinst with java.
Table splitting using R3ta/table splitter can reduce downtime when using machines with lots of CPUsImage may be NSFW.
Clik here to view.
Splitting big tables will mainly distribute portions of the table to different R3trans processes thus ex/importing these tables in parallel...this can save time Image may be NSFW.
Clik here to view.
The migration monitor is the control center for the R3trans processes; it gives you great flexibility in controlling R3trans...
My way of using these tools:
1. start SAPInst (tick the "MigrationMonitor" option one one of the first screens)
2. use Table Splitting feature in SAPInst (using Java)
3. SAPinst will start R3ldctl and R3szchk (creating EXT, STR etc.)
4. when SAPinst prompts for Migration Monitor exit SAPinst
5. split tables using R3ta on os level (= creating WHR files)
6. copy the WHR files to /<export dir>/DATA
7. start migration monitor in background
8. make youself comfortable + drink some coffee Image may be NSFW.
Clik here to view.
9. after migration monitor finishes (and all packages have been processed succesfully) restart SAPinst
10. usually SAPinst will take some minutes to finish...
11. transfer export dump to target directory/machine
12. import uisng SAPinst and migration monitor option...
