SANDBOX REFRESH

1) Export of user master and authorizations from all SAP clients on the target
system (SCC8)
1. "SNBKO00045" for transporting cross-client data, if you have

selected this

2. "SNBKT00045" for transporting client-specific data

3. "SNBKX00045" for transporting client-specific texts, provided texts

are available in this client

2) Please take snapshots of

 Client settings (SCC4)

Logon groups

Processing groups
 AL11, SE03 and SM61
DIR_ATRA E:\usr\sap\SNB\DVEBMGS00\data
DIR_BINARY E:\usr\sap\SNB\DVEBMGS00\exe
DIR_CCMS E:\usr\sap\CCMS
DIR_CT_LOGGING E:\usr\sap\SNB\SYS\global
DIR_CT_RUN E:\usr\sap\SNB\SYS\exe\uc\NTAMD64
DIR_DATA E:\usr\sap\SNB\DVEBMGS00\data
DIR_EXECUTABLE E:\usr\sap\SNB\DVEBMGS00\exe
DIR_EXE_ROOT E:\usr\sap\SNB\SYS\exe
DIR_GEN E:\usr\sap\SNB\SYS\gen\dbg
DIR_GEN_ROOT E:\usr\sap\SNB\SYS\gen
DIR_GLOBAL E:\usr\sap\SNB\SYS\global
DIR_GRAPH_EXE E:\usr\sap\SNB\DVEBMGS00\exe
DIR_GRAPH_LIB E:\usr\sap\SNB\DVEBMGS00\exe
DIR_HOME E:\usr\sap\SNB\DVEBMGS00\work
DIR_INSTALL E:\usr\sap\SNB\SYS
DIR_INSTANCE E:\usr\sap\SNB\DVEBMGS00
DIR_LIBRARY E:\usr\sap\SNB\DVEBMGS00\exe
DIR_LOGGING E:\usr\sap\SNB\DVEBMGS00\log
DIR_MEMORY_INSPECTO
R E:\usr\sap\SNB\DVEBMGS00\data
DIR_PAGING E:\usr\sap\SNB\DVEBMGS00\data
DIR_PERF E:\usr\sap\PRFCLOG
DIR_PROFILE \\DC-VM-SNB\sapmnt\SNB\SYS\profile
DIR_PUT E:\usr\sap\put
DIR_RSYN E:\usr\sap\SNB\DVEBMGS00\exe
DIR_SAPHOSTAGENT C:\Program
DIR_SAPUSERS .
DIR_SORTTMP E:\usr\sap\SNB\DVEBMGS00\data
DIR_SOURCE E:\usr\sap\SNB\SYS\src
DIR_TEMP .
DIR_TRANS \\DC-VM-SNB\sapmnt\trans
EINVOICE_PR I:\usr\einv_res_pr
EINVOICE_UP I:\usr\einv_res_up
EINVOICE_UP D:\usr\einv_res_up
SBI_PR I:\usr\bnk_pr
SBI_UP I:\usr\bnk_up

SM61

SPAD
 Operation modes (RZ03, RZ04 and SM63)

 Logical systems (BD54)

3) Using SE01 transaction, create transport request forbacking up of AL11,
SE03, SMLG(Logon Groups), RZ12(Processing Groups),SM59(RFC’s), SM69,
SPAD, SM61, RZ03

SE01 transaction is used to create transport request in SAP.

As part of pre-refresh steps, we need to take backup of target system’s

 Printer settings (SPAD)

 Processing groups (RZ12)
 Logon groups(SMLG)
 Logical systems (BD54)
 Operation mode settings(RZ03/RZ04)
 RFCs related information(SM59)
 AL11(sap directories)
 SE03 (transport organizer tool settings)
 Batch processing relation information (SM61)
 Customer entries information (SM69)
 Archive related settings (OAC0)
AL11 – User Directory Entries are contained in the following tables

R3TR TABU USER_DIR Keys *

SE03 – System Change Options are contained in the following tables

R3TR TABU TRNSPACEL Keys *

R3TR TABU DLV_SYSTC Keys *

SMLG/RZ12 – Logon Groups and Processing Groups are contained in the

following table.

R3TR TABU RZLLITAB Keys *

SM59 Connections – RFC connections are contained in the following tables

R3TR TABU RFCATTRIB Keys *

R3TR TABU RFCDES Keys *
R3TR TABU RFCDOC Keys *

SALE – Logical Systems are contained in the following tables

R3TR TABU TBDLS Keys *

R3TR TABU TBDLST Keys *

SM69 – Export Customer Entries contained in the following table

R3TR TABU SXPGCOSTAB Keys Y* & Z*

Oca0 – Archive Settings

R3TR TABU CREP_HTTP Keys *

SPAD – Printer Settings

R3TR TABU TSPSV Keys *

SM61 – Batch Processing

R3TR TABU TSRVGRP Keys *

R3TR TABU TSRVLST Keys *

RZ03/RZ04 – Operation Modes & RZ20 settings

R3TR TABU TPFBA Keys *

R3TR TABU TPFHT Keys *
R3TR TABU TPFID Keys *
Save and release the TR before refresh starts

3. Refresh Activity

Make sure source and target have same database version with patchset.

Make sure the filesystem should be same.

Stop Target SAP Database and listener.

Copy Backup, controlfiles and oraarch upto 5-10 min after control file creation to target system.
To create control file:

alter database backup controlfile to trace as ‘location\name.sql’;

Initiate the restore with normal command brrestore –b (.fnd file name) –m all

Meanwhile let’s edit the control file and make it for our target system , and we will use this to create
a control file in our target system.

Delete all before “startup mount” & after “CHARACTER SET UTF8;” in control file. Please note that
there will be a command to create temporary tablespace and those command need to cut from control
file and paste in other notepad and we will use those commands to create temporary tablespace after
database becomes in read write mode.

Change
 <source SID> to <target SID>
 REUSE –> SET
 NORESETLOGS –> RESETLOGS
 Please also look into the directories of sap data files and logfiles and change if require like if
the target system has different directory.

Now save the Control File and we will use it after restoration.
Restoration has been completed.

Now we will restore the controlfile that we have edited and make for target.
The error was occurred because we forgot to delete the already existing controlfile.

So we delete the already existing control file and re-execute the control file creation command

Database status check

Now we will recover the log files
Now we will reset the logs and open the database
Check the database status

Now the database is opened and ready for use but still we will check few parameters.

SAP License has been successfully installed.

Please also create temporary tablespace by editing the command that we have separated while
editing control file

Now we will try to start the sap application and proceed for post activities.
Let’s login with sap and proceed with post tasks

We are able to login with production credentials means source data was completely there.

First we will stop all the background jobs as it is necessary

Import user master for all clients (which was done as part of pre-refresh steps)
Change the client type
Try again

Execute SGEN

10) Remove entries from few listed tables using SE14 transaction

Table List

ALCONSEG
ALSYSTEMS
DBSNP
MONI
OSMON
PAHI
SDBAD
SDBAH
SDBAP
SDBAR
TPFET
TPFHT
TLOCK
SWNCMONI
SAPWLSERV
SWNCMONIINDEX

Execute SE14 and select tables and put the name in field and click on edit
Delete old SAP profiles and import new profiles using RZ10 transaction

Perform spool consistency check using SP12 transaction

Delete old update records using SM13 transaction

Delete/Reorganize transaction RFC’s using SM58 transaction

Delete batch job logs by executing RSBTCDEL report using SE38 transaction

Delete Old spool requests by executing RSPO0041 report using SE38 transaction

Perform mail configuration using SCOT transaction

Delete old mail related entries using SOST transaction