What is the main difference between remote client copy and client
export?
Remote Client copy :-
Remote client copy does not require file system space on OS level. It does not create any files at the OS level. So it is not possible to recreate the same client copy again.
To be able to copy all the data during copy, the structure of all copied tables in both the systems must be identical. An automatic repository check will be performed for every remote client copy. CC will be failed, if inconsistencies are detected. Inconsistencies must be removed before starting CC.
This is one step process (remote CC through Scc8).
RFC connection is required.
CC can be used with multiple parallel processes.
Remote CC is better if you have small data to be copied.
Remote CC can not be done from OS level.
Remote CC might be little bit slower than the export due to its network constraints.
Need to check Network, Database ( generation of archive logs, table space usage ) through out the CC.
Export-Import :-
Client export require sufficient file system space at OS level (ex: E:\usr\sap\trans) since it creates a big dump file at OS level (data & cofiles). It is possible to recreate the same client copy later.
This problem may not be there in export-import.
This is 3 step process ( export- import-post processing).
RFC connection is not required between systems.
Multiple parallel processes can not be used.
Export-import is generally used for copying larger amount of data.
Export-import can be done from OS level exception is post processing.
Export-import is relatively faster than the remote CC.
Need to check DB constraints at the import process.
Remote Client copy :-
Remote client copy does not require file system space on OS level. It does not create any files at the OS level. So it is not possible to recreate the same client copy again.
To be able to copy all the data during copy, the structure of all copied tables in both the systems must be identical. An automatic repository check will be performed for every remote client copy. CC will be failed, if inconsistencies are detected. Inconsistencies must be removed before starting CC.
This is one step process (remote CC through Scc8).
RFC connection is required.
CC can be used with multiple parallel processes.
Remote CC is better if you have small data to be copied.
Remote CC can not be done from OS level.
Remote CC might be little bit slower than the export due to its network constraints.
Need to check Network, Database ( generation of archive logs, table space usage ) through out the CC.
Export-Import :-
Client export require sufficient file system space at OS level (ex: E:\usr\sap\trans) since it creates a big dump file at OS level (data & cofiles). It is possible to recreate the same client copy later.
This problem may not be there in export-import.
This is 3 step process ( export- import-post processing).
RFC connection is not required between systems.
Multiple parallel processes can not be used.
Export-import is generally used for copying larger amount of data.
Export-import can be done from OS level exception is post processing.
Export-import is relatively faster than the remote CC.
Need to check DB constraints at the import process.
0 Comments