1.1.

Save RFC Destinations Please use the Dummy Buffer called XXX
 Client Independent
 Enter transaction se09
 Choose Request/task  Create
 Choose Workbench request, hit ok
 Enter Short Description
o Example: RFC Connections for <SID> - <DATE>
 Click on task transport
 Choose Request/task  Delete
 Choose Request and Choose Reqeust/task  ObjectList Display Object
List. Or double click in the request and then click the change button.

 Choose Object List  Display < - > Change

 Enter R3TR  TABU  RFCDES

 Double Click on Entry just added
 Double click again the the first empty line.

 Click on Key Fields button

 Enter * into Val. Field
 Hit enter

 Click on Save button

 Repeat for: RFCDOC
RFCDESSECU
RFCATTRIB
RFCCHECK
RFCGO
RFCTA
RFCSYSACL
RFCTRUST
RFCTYPE
o Total of 9 tables
 RFCCMC, RFCSTXTAB, (These are not necessary now, since
they have typically empty)
 Click on Save
 Click on Back, Choose Request/task  Release Directly

 Record Transport Number and Verify cofile and data file exist at UNIX
level
o As <sid>adm
o <sid>adm> cd /usr/sap/trans/cofiles
o <sid>adm> ls -l <Transport Number>.<SID>
 o <sid>adm> cd /usr/sap/trans/data
o <sid>adm> ls -l <Transport Number>.<SID>

1.2. Save Distribution Models

* Please use the Dummy Buffer called XXX
 Log into client 510 (Distribution Model and Partner Profiles are Client
Dependent)
o Enter transaction BD64
 Highlight each Model View

 Choose Edit  Model View  Transport

 Click on Create Request

 Enter Short Description
  Ex: Distribution Model for <SID> - <DATE>
 Enter Buffer Name and Client

 Record Transport Number

 Repeat for each Model View
 Enter transaction SE01
 Enter transport number
 Choose Request/task  Release  Directly (save to appropriate Dummy buffer)
o Ex: XXX
 Repeat for each Client
 Record Transport Number and Verify cofile and data file exist at UNIX level
o As <sid>adm
o <sid>adm> cd /usr/sap/trans/cofiles
o <sid>adm> ls -l <Transport Number>.<SID>

o <sid>adm> cd /usr/sap/trans/data
o <sid>adm> ls -l <Transport Number>.<SID>
1.3. Partner Profiles
 Save Partner Profiles via SE09 (ONLY 4.6C)
o Login into Productive Client, i.e. 510
o Enter transaction se09

o Choose Request/task  Create

o Choose Workbench request, hit ok

o Enter Short Description

 Ex: Partner Profiles for <SID> - <DATE>
o Click on task transport
o Choose Request/task  Delete
o Choose Request and Choose Reqeust/task  ObjectList Display
Object List
Choose Object List  Display < - > Change
o Choose Edit  New Entries
o Enter R3TR  TABU  EDIPHONE

 Double Click on Entry just added

 Doubble click in the first line
 Click on Key Fields button
 Enter * into Val. Field
 Click on Save button
 Repeat for the following tables: EDMA
EDMAT
EDMMS
EDP12
EDP13
EDP21
EDPAR
EDPI1
EDPO1
EDPO3
EDPP1
 EDPPV
EDPVW
EDIPOD
EDIPOA
EDIPORT
 Total of 17 Tables

 Click on Back, Choose Request/task  Release Directly

 Record Transport Number and Verify cofile and data file
exist at UNIX level
 As <sid>adm
 <sid>adm> cd /usr/sap/trans/cofiles
 <sid>adm> ls -l <Transport Number>.<SID>

 <sid>adm> cd /usr/sap/trans/data
 <sid>adm> ls -l <Transport Number>.<SID>
 1.4. User master Records and Security Roles

Use transaction SCC8

Handover the system to the DBa for the redirected restore process.

1. Review the documentation, especially for specific system refreshes like BI, etc.
2. Back up everything needed, for example, RFC connections, packages, printers,
distribution models, profiles, users, etc.
3. Shutdown the system and handover it to the DBA
4. Try to start SAP system and if you receive an error regarding to the connection to
the database can not be stablished please be sure you are using the correct
“schema”. Remember the you are bringing the database from another system and
may be the name of this source system is different,and because that the “schema
is different. If this is the case be sure that the following environment variable is
correct:
a. dbs_db6_schema=<source system schema>
b. If it is necessary please set the environment variable in the user profile
i. /home/<sid>adm/ .cshrc
ii. /home/<sid>adm/.dbenv_hqsappe0.csh
5. Try to start sap system and if it shows an error regarding to R3trans connection,
run R3trans –d and check trans.log file may be you will find an error like that:

4 ETW000  [dev trc     ,00000]    (0.99) DB6: SUBSTITUTE VALUES with FAE statements (note
1028779)
4 ETW000                                                                              52  0.016923
4 ETW000  [dev trc     ,00000]  Supported features:                                   32  0.016955
4 ETW000  [dev trc     ,00000]  ..retrieving configuration parameters                 33  0.016988
4 ETW000  [dev trc     ,00000]  ..done                                               209  0.017197
4 ETW000  [dev trc     ,00000]  Running with UTF-8 Unicode                            33  0.017230
4 ETW000  [dev trc     ,00000]  *** ERROR in DB6Connect[dbdb6.c, 1636] CON = 0 (BEGIN)
4 ETW000                                                                           42609  0.059839
4 ETW000  [dev trc     ,00000]  &+     DbSlConnectDB6( SQLConnect ): [IBM][CLI Driver]
SQL1326N  The file or directory "/db2/BIS/sapdata1/db2bis/NODE0000
4 ETW000                                                                              57  0.059896
4 ETW000  [dev trc     ,00000]  &+     /sqldbdir/sqldbdir" cannot be accessed
4 ETW000                                                                              56  0.059952
4 ETW000  [dev trc     ,00000]  &+
4 ETW000                                                                              55  0.060007
4 ETW000  [dev trc     ,00000]  &+
4 ETW000                                                                              57  0.060064
4 ETW000  [dev trc     ,00000]  &+
4 ETW000                                                                              55  0.060119
4 ETW000  [dev trc     ,00000]  *** ERROR in DB6Connect[dbdb6.c, 1636] (END)          35 
0.060154
4 ETW000  [dbdb6.c     ,00000]  *** ERROR => DbSlConnect to 'BIS' as 'sapbis' failed
4 ETW000                                                                              95  0.060249
2EETW169 no connect possible: "DBMS = DB6                              --- DB2DBDFT = 'BIS'"
 6. Be sure that the “<sid>adm” and “sap<sid>” from the source system exist on the
target system, and be sure they have the correct password. If the users don’t
exists, create them using SMITTY

If this is the error please it is because the permissions for the users sap<surce id> and
<source id>adm please make sure they are members of the following groups:

<target id>adm  db<target id>adm,db<target id>ctl

Example:

sap<source id>  db<target id>mnt

Example:
If the system still can not start and testing with “R3trans” tool you may will find the
following error in “trans.log” file :

hqsapsa0:scsadm 12> cat trans.log

4 ETW000 R3trans version 6.14 (release 701 - 19.01.11 - 11:44:00).
4 ETW000 unicode enabled version
4 ETW000 ===============================================
4 ETW000
4 ETW000 date&time : 02.09.2011 - 09:08:01
4 ETW000 control file: <no ctrlfile>
4 ETW000 R3trans was called as follows: R3trans -d
4 ETW000 trace at level 2 opened for a given file pointer
4 ETW000 [ dev trc,00000] Fri Sep 2 09:08:01 2011
361 0.000361
4 ETW000 [ dev trc,00000] db_con_init called 32
0.000393
4 ETW000 [ dev trc,00000] create_con (con_name=R/3)
59 0.000452
4 ETW000 [ dev trc,00000] Loading DB library
'/usr/sap/SCS/SYS/exe/run/dbdb6slib.o' ... 49 0.000501
4 ETW000 [ dev trc,00000] DlLoadLib() success:
dlopen("/usr/sap/SCS/SYS/exe/run/dbdb6slib.o"), hdl 0
4 ETW000 1158 0.001659
4 ETW000 [ dev trc,00000] Library '/usr/sap/SCS/SYS/exe/run/dbdb6slib.o' loaded
34 0.001693
4 ETW000 [ dev trc,00000] function DbSlExpFuns loaded from library
/usr/sap/SCS/SYS/exe/run/dbdb6slib.o
4 ETW000 54 0.001747
4 ETW000 [ dev trc,00000] Version of '/usr/sap/SCS/SYS/exe/run/dbdb6slib.o' is
"700.08", patchlevel (0.135)
4 ETW000 596 0.002343
4 ETW000 [ dev trc,00000] function dsql_db_init loaded from library
/usr/sap/SCS/SYS/exe/run/dbdb6slib.o
4 ETW000 50 0.002393
4 ETW000 [ dev trc,00000] function dbdd_exp_funs loaded from library
/usr/sap/SCS/SYS/exe/run/dbdb6slib.o
4 ETW000 50 0.002443
4 ETW000 [ dev trc,00000] New connection 0 created
40 0.002483
4 ETW000 [ dev trc,00000] 000: name = R/3, con_id = -000000001, state =
DISCONNECTED, tx = NO , hc = NO , perm = YES,
4 ETW000 reco = NO , frco = NO , timeout = 000, con_max = 255,
con_opt = 255, occ = NO
4 ETW000 82 0.002565
4 ETW000 [ dev trc,00000] db_con_connect (con_name=R/3)
70 0.002635
4 ETW000 [ dev trc,00000] find_con_by_name found the following connection for
reuse: 32 0.002667
4 ETW000 [ dev trc,00000] 000: name = R/3, con_id = 000000000, state =
DISCONNECTED, tx = NO , hc = NO , perm = YES,
4 ETW000 reco = NO , frco = NO , timeout = 000, con_max = 255,
con_opt = 255, occ = NO
4 ETW000 78 0.002745
4 ETW000 [ dev trc,00000] *** ERROR in DbSlConnectDB6[dbsldb6.c, 1276] CON
= 0 (BEGIN) 854 0.003599
4 ETW000 [ dev trc,00000] &+ DbSlConnectDB6: can't find user 'sapscd' in
'/usr/sap/SCS/SYS/global/dscdb6.conf'
4 ETW000 63 0.003662
4 ETW000 [ dev trc,00000] &+
4 ETW000 58 0.003720
4 ETW000 [ dev trc,00000] &+
4 ETW000 59 0.003779
4 ETW000 [ dev trc,00000] &+
4 ETW000 75 0.003854
4 ETW000 [ dev trc,00000] *** ERROR in DbSlConnectDB6[dbsldb6.c, 1276]
(END) 36 0.003890

7. This error is probably because the new created users need a new password, to
solve the problem try to login to the system with the <sid>adm and sap<sid>
users and change you will be asked to change the passwords for the first time.
Then rewrite the file “dscdb6.conf” using the following command:

 With <sid> credentials run the command

 dscdb6up –create [<source sid>adm user password] [sap<source sid> user
password
 ej. dscdb6up –create pass1 pass2

8. Only for SCM systems. In the case of a system running on DB2 9.7 some
additional steps need to performed in the target system from the database
administrator and also the basis team needs to run a script qith <sid>adm
credentials. The script name is bbb.ksh.

hqsapsa0:scsadm 7> ksh to switch to a k shell

$./bbb.ksh to execute the script
Post Processing

1. In order to prevent batch jobs to run in an inappropriate manner, it is

recommended to modify the instance profile and reduce the number of batch
processes to cero.
a. /sapmnt/ECD/profile/ECD_DVEBMGS00_hqsapde0
b. rdisp/wp_no_btc = 0
2. Restart SAP system
3. Apply for a new license and install it.
4. You can use BTCTRNS1 program to lock al the batch jobs while you finish the
system copy process and make sure all of them will run as need it. Then you can
use BTCTRNS2 to unlock them. Run BTCTRNS1 program to pause any other job
until the system copy is finished.
5. Change the rdisp/wp_no_btc parameter to its previous value
6. Restart SAP system
7. Run an installation check: Administration System administration Administration
Installation Check (transaction SM28).
8. In case you have DB2 9.7 and you are getting the short dumps described bellow,
it will be required to apply a solution which consist of running a script which
corrects the issue at DB2. According with some research the name of the
tablesspaces need to be changed in some control area inside DB2. To do it, it is
needed to run the following command.

db6util -rtvt $a $b
We created a script bbb.ksh that includes the command.

# !/bin/ksh
# ########################
#
# bbb.ksh
#
#
#
#
# ########################

# this runs against the DB2DBDFT database

IFS=" "
while read a b; do

db6util -rtvt $a $b

done < aaa

Run the script with <sid>adm credentials

Switch to k shell
hqsapsa0:scsadm 17> ksh

The execute the script

hqsapsa0:scsadm 19> ./bbb.ksh
It will take some time to run.

9. In order to refresh the Live Cache system for a SCM system check the SAP notes
886103, 877203 and 457425. Basically use the backup restore procedure and re
configure the connections from LC10 transaction.
a. Once you restore Livecache, make sure you connect using
<source_id>adm user credentials to connect. You have to configure this in
Livecache “integration” screen in LC10 transaction.
b. Also you have to delete a couple of tables from LiveCache database
according to 1015489 note.
c. Finally use /n/sapapo/OM13 transaction to check LiveCache and meke
sure there are no errors.
10. Inactivate or delete the partner profiles that came with the system copy from the
source system.

11. If the target system is a recently created system (new) and the kernel patch is not
the same version as the source system, is recommended to update the kernel now,
before continue. In that case you should restart the system.

12. Configure the Workbench Organizer (transaction SE06) with the option Database
Copy. This releases all transport, repair, and customizing requests that have not
been released in the source system.
13. Adapt the transport parameters and transport routes in the Transport Management
System (TMS):
14. Restore RFC connections, distribution models and partner profiles from the
original system if it is required.
15. Delete all entries from the following tables: ALCONSEG, ALSYSTEMS,
DBSNP, MONI, OSMON, PAHI, SDBAD, SDBAH, SDBAP, SDBAR, DDLOG,
TPFET, TPFHT, TLOCK
16. Delete batch jobs, according to your needs.
17. Because we deleted the contents of TPFET and TPFHT tables at this point is good
idea to go to RZ10 transaction to import the profiles from active servers.

18. Check the consistency of the Temporary Sequential Objects

(TemSe) by searching for files of TemSe objects for which no
TemSe objects exist:
19. Adapt the definition of the printers to meet the new system
requirements. If required.

20. Start transaction SECSTORE using Check Entries. If you find

erroneous entries with message text System-dependent data for
entry … changed , see SAP Note 816861.
21. Check logon groups and assignment of application servers to
logon groups (transaction SMLG).
22. Reeschedule the standard House keeping jobs and RDDIMPDP
with RDDNEWPP program from client 000. If you deleted all the
batch jobs previously.

23. Make sure that the parameter login/system_client has the value
of the new client, the working client for the target system, in this
case 100.
24. Deactivate FAX and email nodes so documents won’t be send by
any automatic process or job. In order to do it go to transaction
SCOT.
 25. Please don’t create the “logical system name” for the new
created client, it will be created automatically when the next
step is executed with the transaction BDLS.

26. If you want to rename one or more of the copied systems, then
execute Transaction BDLS both in the client you wish to rename
and in all the connected BW-systems and source systems.
Please read the notes 121163 and 369758 regarding details
about transaction BDLS.
a. Excluding big tables from BDLS execution. Execute the
following procedure if it is required, normally it is for big
databases

SM30
List of biggest tables in ECP SAP system.
CE11001
COEP
FAGLFLEXA
VBFA
ACCTHD
COBK
FAGLFLEXT
FAGL_SPLINFO
LIPS
SRRELROLES
VBAK
VBRP
BKPF
STXH
b. BDLS execution
27. For ECC for disputes please check every individual client in the
system and if it is necessary run DBLS for client specific data in
every related client.

28. If after the conversion with BDLS transaction you try to run the
RSA1 transaction in the new working client and you are receiving
the the error “You may anly work in client XXX” you can change
that using the function module RS_MANDT_UNIQUE_SET
(Transaction SE37). You can find little more information in note
316923.

29. Reactivate all partner profiles that carry the new logical system
name after renaming Execute Transaction WE20 to reactivate
the partner profiles. Choose "Partner type LS (logical
system)" enter the logical system name of the partner  in tab
"classification", change the  partner status from "I" (inactive) to
"A" (active) and save.
30. BW and SCM: Update logical system descriptions in RSA1 For
each source system that was converted using BDLS change the
description to match the new logical system name.
31. BW: Adjust server name of the BI Enqueue Server, if BI Planning
is used If you are using BI Planning, adjust the server name of
the BI Enqueue Server in the administration transaction RSPLSE.
For details please check note 996238.
32. Reset generation flag for ODS activation programs Call
transaction RSSGPCLA and highlight program class
RSDRO_ACTIVATE. Click #set status# and #OK#. Repeat the
same for program class RSDRO_EXTRACT and RSDRO_UPDATE
33. BW: Update the RSLOGSYSDEST with the new destinations for
the source systems.
34. BW: Reset RFC destination for process chain transport post
processing. Use transaction RSTPRFC. By default, you will see
SIDix100 for the source system.
 35. BW and SCM: Restore Check the source system
Note: Be sure that the newly crerated the source system is open for
modifications
Note: Be sure that the newly created the source system is open for
modifications
36. Verify the specific paths in AL11 transaction for the source
system and if something needs to be changed please proceed.
37. For transport Workflow functionality be sure TMSADM user in
client 000 has sap_all permissions.
38. BW: Check table RSBASIDOC in the newly copied target SAP
source system to determine all existing source system
connections.
39. SCM:Configure RFC connection for various application cases in
SCM systems.
Navegate to
ECSCIFADM_TRUSTED
40. Adjust the operation modes in transaction RZ04.
41. Ajust RZ12 transaction accordingly.
42. SCM: Adjust the the DBA planning calendar for LiveCache in
order to perform the consistency check and the database
backup.