SAP Client Copy: Local, Remote, Import/Export

Details

Last Updated: 06 January 2021

Client Import/Export: - This method is used to copy client between different instances(SID).It is performed by T-code SCC8 To avoid data inconsistencies there are few pre-steps to be performed before starting client copy:-
1) Disconnect and lock business users(SU10).You can end the session of active users in the system through SM04. Once all users are logged out, check that no canceled or pending update requests exist in the system.
   2) Suspend all background jobs

• Execute SE38 as given below.

• Fill program name with "BTCTRNS1" as above figure.
•  Press Execute.

3)  For a local copy, the system must have enough space in the database or tablespace.
For remote copy, target system must have enough space in the database or tablespace. Check space using Tx DB02. 4) To avoid inconsistencies during client copy users should not be allowed to work in source client.

5) rdisp/max_wprun_time parameter should be changed to 2000 second as a SAP recommendation . Although you use parallel processes and schedule job in the background, dialog processes will be used.
 

Local Client Copy

Local client copy is performed using Tcode SCCL.
Scenario:-

• Source Instance & client := DKM-000
• Target Instance & client := DKM-202

Step 1) Create an entry for your new target client using SCC4. In our scenario, we will create client 202 in DKM system.Log on to this newly created target client (DKM-202) with user SAP* and default password pass.

Step 2) Excute T-code SCCL. Step 3)

• Select your desired profile
• Enter Source client.
• Enter Description

Step 4) By default Client Copy is executed as a single process. A Single process will take a lot of time. We will distribute the workload of single the process to parallel(multiple) processes which will reduce time in copying a client.

1. Select Goto from the menubar.
2. Select Parallel Process.Parallel processes are used to exploit the capacity of database better

Step 5) Always execute long running processes in background mode rather than foreground/dialog mode. In fact, some processes run more quickly in the background. Step 6) The client copy logs are available in SCC3. Status - "Successfully Completed" means client copy is completed. This technique uses Remote function call. You can view RFC from SM59. This technique depends on the network, so network connectivity must be strong enough.

Scenario:-
Source Instance & client := BD1-101
Target Instance & client := DKM-202
Step 1) Log on to the target system. Here we will log on to DKM system. Create a new target client entry(202) using SCC4. Log on to this new target client with user SAP* and default password "pass".Here we will log on to DKM-200 system.

Step 2) Execute Transaction Code SCC9.
  Step 3) Fill the basic details as per your requirement.
  Step 4) Select Parallel Process.Parallel processes are used to exploit the capacity of database better.
  Step 5) Schedule the client copy in background
  Step 6) The client copy logs are available in SCC3 as given below.
 

 

For large database, it is recommended to use client import/export instead of remote client copy.
Scenario:-
Source Instance & client := PKT-300
Target Instance & client := DKM-202
This technique always starts with client export step.

Note: - You must have enough space in the /usr/sap/trans_SID file system to perform the client export.

How to export client?;

Step 1) Log on to the target system(DKM). Create an entry for your new target client using SCC4. Log on to the source system/source client(PKT).

Step 2)Before you import a Client you need to export.Export is nothing but transferring data files and co-files from source system's database to target system's import buffer.Execute T-code SCC8.
   Step 3) 

• Select profile
• Choose target system.

YOU MIGHT LIKE: