Hi,
Have you analyzed SM21, ST22 , SCC3 logs?
Also check the CPU/Memory availability at Source & Target Systems. Two copy processes per CPU count are recommended.
Have you disabled Archive log mode in ur QAS system before performing actual Client Copy, this can be helpful in speedup the client copy process ? Before activating/deactivating archive mode Offline backup of System DB is recommended to guarantee the Complete DB Recovery.
DB Reorganization and Updating DB Statistics in Source system's DB before Client copy, can speedup the Client Copy process.
Regards,
Bhavik G. Shroff
HI Bhavik,
For sm21, st22 and scc3 everything are fine. No error found and the copy was fine, the only thing is too slow.
CPU/Memory availability at Source & Target Systems -> for this one i think i not really check. Maybe next run I will
check on it. Let say CPU/memory is in too high usage what shall I do? Stop the copy and perform a stop/start sap and
after that restart the client copy? Is it working with this way?
Archive log has been disabled. For update statistics, it already ran one hour before the client copy start. Only thing I not perform here is db reorganization.
Any other way? Some said that by doing client export and import. Anyone know the step? Maybe someone can provide
me the step.
Thanks.
> Any other way? Some said that by doing client export and import. Anyone know the step? Maybe someone can provide
> me the step.
I suggest just checking the documentation:
http://help.sap.com/saphelp_nw70ehp1/helpdata/en/69/c24c0f4ba111d189750000e8322d00/frameset.htm
Markus
Solution is by doing client export and import.
It's really fast by doind client export/import
than doing remote client copy.
