Remote client copy

Complete steps without any error

1. Remote Client Copy
Preparation
Please reset user sap* on db level in target system ; as it is locked automatically during post
processing in client copy
Please read note 568784 Termination with client copy local or Remote (Financial Basis)
Because local or remote client copy generates error after all post processing steps performed which are
under as
o FINB_TR_CC_EXIT_TARGET (Application Exit Error)
o MDG_TR_CC_EXIT_TARGET (Application Exit Error)

o Logon to target client with user SAP*

o Create RFC connection from target client to source client using t-code FINB_TR_DEST or
SM59

 E.g FINBTR@PRDCLNT450 or any example: TRN_ATF
 Destination: Source System
 User: Tkhan (User must exist in source System)
 User type: System or communication(In source system)

o Note: Please use system or communication user with RFC connection from target to
source system with SAP_ALL and SAP_NEW authorizations

o During first step the system check RFC dictionary objects on both system source and
target

 if tables or fields are missing on remote system then these tables or fields are
copied in the target without excluding them using report (RSCCEXPT)
 if tables or fields are missing on local system then you have to adjust those
tables or fields or exclude them from the source system after confirming from
functional consultants.

o Please run report RSCCEXPT on both source and target systems to check either tables
are excluded or not on both systems. You should only excluded tables in source system
if you don’t want to copy on target system. Please also check tables on target system as
well as these tables would not copied on target system if these exists on source system.

o Disconnect and lock other dialog users.

2. o Suspend background jobs :

 This can be done using report BTCTRNS1. The jobs will be released afterwards
using report BTCTRNS2.

o For remote client copies, the data dictionaries between the source and target systems
should be the same.

o If not, in case of client copy between a production and development system, you can
exclude tables from the client copy using report RSCCEXPT. You have to be sure that
your target client will still be usable and consistent compared to your needs depending
on the table excluded

o Please create logical system using BD54 during remote client copy which points to
source system with its client number, don’t enter language; Use system or
communication user in target client with full authorizations

Pre-Steps
 You must have sufficient disk space in database by adding more data files on database level
 Adjust memory parameters to maximum values depending on hardware
 Set parameter login/no_automatic_user_sapstar = 0 on target system
 Set parameter rdisp/max_wprun_time = 0 on both source and target system
 Set parameter rdisp/wp_no_dia = 40 -50 on both source and target system (When you are using
parallel processes, these dialog work processes will be used in source and target systems)
 Set parameter rdisp/wp_no_btc = 8 or 10
 Add more db log files at db level to speed up loading data on target system
 Users should not login to source and target system (Please lock dialog users)
 Set overwrite mode = overwrite on Target system to avoid taking log backup again and again
 You must set AutoLogbackup = OFF on db-studio because lots of LOG backup has to be taken if
you choose AutoLogbackup = ON
 Suspend background jobs using SE38->BTCTRNS1
 You can also exclude tables on source system which are not on target system by using SCC9
o Source system
o Choose menu Edit->expert setting
o Select tab table and enter tables which you don’t want to be imported on target system
 For COPA missing tables and fields please after discussion with CO Consultant import below
mentioned transport
o DEVK913144 : COPA 01
o DEVK913146 : COPA 02

3. Execution Steps:
 Create client using SCC4
 Logon to newly created client
 Create RFC connection from Target to source system
o Check connection
 SCC9
 Select profile and source destination
 Chose icon parameter for parallel processes (Set according to work processes) then save
 You can test run to estimate time and space required for remote client copy
 You can schedule remote client copy with time or immediately
 For Log choose SCC3
 Remote client copy cancels at RBDLSMAP phase
o SCC4 and uncheck option: Locked due to Client copy
o Logon with dialog user
o Implement SAP Note: 0001754066 with dialog user
o Restart SCC9
Post Steps
 Logon to newly created client with SAP*
 SICK: For consistency and installation check
 SE06: Select database copy, click post installation processing after client copy
 STMS: (On client 000), check and recreate if necessary
 SE38: run RSBTCDEL
 RZ04: delete old instance schema and regenerate new one
 Resuming Suspended background jobs :
o SE 38 jobs will be released afterwards using report BTCTRNS2.
 SM37: reschedule all non system jobs/ Delete if required
 SM36: Create jobs standards (Default scheduling) and suppress duplicate jobs / Using DDIC user
 SCC4: Change role accordingly
 RZ10: Execute import profiles of active servers
 DB13: reorganize jobs if scheduled
 Check SM21, ST22 and SP01 for any errors and troubleshooting
 If during remote client copy step RBDLSMBAP failed then try to restart after applying note,
otherwise you will have to run transaction code BDLS to change the logical system name and
adapt to the new system.

4. Errors during client copy:
1. During remote client copy there are long running tables gets locked? How to unlock
Solution:
You can restart client copy again after all processes get completed. Please check whether restart
mode active?

2. RDBLMSAP: Client copy cancelled again and again
The system is trying to convert logical system name for running client. This process is necessary
and should not be avoided
Solution
Implement SAP Note: 1754066
The mentioned note cannot be implemented with SAP* user. Try to implement with dialog user.
Following are steps to implement and unlocking of client temporarily
 You have to unlock client for other dialog administrator user to implement this note
 Unlock client in scc4
 Uncheck option locked due to client copy
 Logon with dialog administrator user
 Implement note: 1754066
 Logout administrator user
 Restart client copy with SAP* and please note that restart mode should be active