Long running time at system copy

[Former Member]

Hi All,

I met a problem while performing system copy. system environment is: win server 2003 Oracle 10g

the export process runs smoothly until the 19th package be exported.

18 out of 19 package have been exported successfully.

The last package is SAPSSEXEC.XXX, I checked the log file and found it runs for long time on table IGORA, PERMISSION, REPOSRC. IGORA took 2 hours more, PERMISSION took 4 hours, and REPOSRC still havn't been completed due to it contains 20 million records, but strange is that IGORA only contains 15 entries, why it took so long? and as checked in SE11, this table doesn't contain any LONG type field.

before system export, I already updated oracle statistics.

I have read through sap note:

Note 1046103 - ORACLE DIRECT PATH LOAD SUPPORT IN R3LOAD 7.00 AND LATER

Note 936441 - Oracle settings for R3load based system copy

Note 1045847 - ORACLE DIRECT PATH LOAD SUPPORT IN R3LOAD7

But seems not helpful.

Could any expert help me?

Thank you very much

[Former Member · Accepted solution]

Hi,

You can compare REPOSRC.log and REPOSRC.log.bck file it's copying or not.

Check the SIZE of the tables.

The Below points will use to increse the system performance while exporting.

1. Using of RowID splitting for large transparent tables (PL/SQL Script) (Table spliiting)

3. Increasing CPU/RAM in the Source hardware.

4. Editing DDLORA.TPL file for reducing index creation of import, copy parameter from DDLORA_LRG.TPL file

5. delete data from batch logs table (APQD, EDI40, TST03....)

6. Update Full statistics before export using the below br command

Brcoonect -c -u / -f stats -t all -f collect -p <number of CPU>

7. Disable archiving in database

(alter database noarchivelog)

8. PSAPTEMP adjustments , DB parameters as per the note 936441

9. for oracle slow I /O performance check the note 834343, 793113

Regards,

Ram

[Former Member · Accepted solution]

thank you so much Ram, problem has been solved finally.

your suggestions are helpful to me although I read these notes before but I didn't have a try:)

I split big packages into many small ones thus finally solved the problem, still long running but finally can be success, the long running time I think is due to the poor performance of my hard disk. I use another stronger disk to test, the speed seems faster than this one.

[Former Member]

Hi Zifang,

Have a look at this eBook, it's got some great tips on how to speed up system copies

You'll be able to improve BDLS performance to run in a fraction of its normal run time.

Regards,

Olly

[Former Member]

Hi,

What are the specs of the server?

Did you check the logs to see if there were any resource deadlocks at that time?

Regards,

Shitij