Client Copy Pre-steps,Local Client Copy

Client Copy Pre-steps

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 cancelled or pending update requests exists 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 , 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 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. Single process will take a lot of time.We will distribute workload of single process to parallel(multiple) processes which will reduce time in copying a client.

1. Select Goto from 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. Infact, some  processes run more quickly in background.

Step 6) The client copy logs are available in SCC3 . Status - "Successfully Completed" means client copy is completed.