client import taking too long

[Former Member]

Hi All,

I have started client import which is running since 5 day's, and there is no end in sight, iformation as follow:

1. client size ca. 1.7 TB

2. largest table ca. 1.4TB

3. Client export "transport" size ca. 105 GB

4. R3trans is active since 5 day's

5. Oracle process is active since five day's

The only thing log file I see is a follow:

ETW690 COMMIT "110600" "1418052747247"

4 ETW690 COMMIT "110600" "1418052857847"

4 ETW690 COMMIT "110600" "1418052968447"

4 ETW690 COMMIT "110600" "1418053079047"

4 ETW690 COMMIT "110600" "1418053189647"

4 ETW690 COMMIT "110600" "1418053300247"

4 ETW690 COMMIT "110600" "1418053410847"

4 ETW690 COMMIT "110600" "1418053521447"

4 ETW690 COMMIT "110600" "1418053632047"

4 ETW690 COMMIT "110600" "1418053742647"

I have no idea what exactly system is doing, or what not, there is no other log file is available, in transport queue "import monitor" is telling that import is in "Main Import" phase since 5 day's.

Is there someone who can help, or was having same issue.

Thanks

for your help in advance.

[Former Member]

Hi,

The only disadvantage of using Export/Import is .. you cannot look for the status till the import gets finished.

Only way you can guarantee that the import is running by checking the R3trans process in your top cpu list in st06.

Instead of Export / Import , You can probably go for remote copy with using Parellel processes for the client copy which will be more faster as we use parellel processing.

But the best way is to go for a system copy instead of a client copy.

Thanks,

Jagadush

[Former Member]

Hi Gurus,

Meanwhile my client copy has broken due to HW failure, to restart I have following questions:

1. Can I restart the process in STMS, without any exception.

2. Will SAP restart the process from the begining, or it will start where it was broken

3. What will be the time loss factor, if restarting

4. If I decide to start from scratch what tables can I exclude to speed up the export / import process, does some has list of

tables to be excluded.

5. What is teh best practice for large client export / import.

Please reply.

Thanks

sahmad

[Former Member]

Hello,

I would suggest you to look at the DB Size and the number of recods gettig added int the Largest Table which you menioned.

This way you will be able to calculate the expected runtime.

In addition to that, have a lok at the OS Level Processes such as R3trans (CPU and Memory Utilization),

Thanks

PrakashP

[sunny_pahuja2]

Hi,

For such a large client, system copy is the recommended method as client copy will be too slow for such large clients.

Apart from that, have you switched off the archiving for the target client ?

Thanks

Sunny