Learn SAP Easy

SAP System Refresh:

Copy of existing system (PRD) to another existing system (QAS). System refresh means copying the production (PRD) data on to the quality (QAS) to test the real data.

Process:

1. PRE STEPS

2. DB REFRESH

3. POST STEPS

Overview of refresh:

Pre Steps on the Target system (In this case it is QAS). It is required to keep the dependencies of the target system to restore them later i.e. after refresh.

Ex: After Refresh, the target system QAS behaves like production System. Se we need to delete the source dependencies and restore the target dependencies, Users, RFC Connections, Batch Jobs, License, Printers, and Roles etc.

Take a copy of them using transport requests, screen shots etc.
Delete the entire SAPDATA files from target QAS System
Backup and generate the control file from source system PRD.
Restore the database from Tape or Disk.
Create Control file with new database structure of QAS after modifying S_SID with T_SID.
Make the BTC Processes to zero (0) so that no background job is trigger
Start the system and restore the target dependencies (post-activities)

Pre-refresh activities:

Create the transport of copies by using SE01 and specify the following objects/ tables USR01, USR02, RFCDES and TBDLS and then we need to release the Transport of Copies.- Copy the cofiles & datafiles in usr\sap\sid\trans
Take the screen shots of SM59, BD54, DB13, SM37, AL11 (All the SAP Directories), WE20 (IDOCS), SMLG, RZ12 (RFC SERVER GROUPS), RZ70 (In order to populate the backend system details to SLD), RZ04 (Operation Modes) SCC4, SPAM.
Then, we need to delete all the data files related to QAS system. sapdata1, sapdata2 etc. First, we need to stop the oracle services. The structure should remain same. Directories like sapdata1... sapdata...n, MirrorlogA/B, OriglogA/B

Actual Refresh activities:

Performing Refresh Activity on Database of PRD (Source)

Coming to Production (PRD),

Take offline backup (located under \orcale\PRD\sapbackup\<filename>.afd. Copy <filename>.afd and paste in \oracle\QAS\sapbackup structure folder of QAS system and generate control file by following command SQL> alter database backup controlfile to trace. Find the trace file in the following location “D:\oracle\PRD\saptrace\usertrace”. Check the latest file that is-generated.
Copy that file and paste it onto the Desktop of QAS system. Modify the file as following Rename the file to control.sql.
Remove all the content above the line STARTUP NOMOUNT and below CHARACTER SET URF8

Replace NORESETLOGS with RESETLOGS.

Replace ARCHIVELOG with NOARCHIVELOG.

Replace Source <SID> with Target <SID>
In addition, copy paste (control.sql) in \oracle\QAS\sapbackup.
Open the .afd backup file (Ex. bdjvujux.afd) present in sapbackup directory. Replace the PRD with the QAS and save it.
Now, restore the database

Check the presence of the paths for the creation of the control files oracle\oracle\QAS\origloga\cntrl

\oracle\QAS\origlogb\cntrl

\oracle\QAS\sapdata1\cntrl

If one of these paths is not present, create it.
Start the services of Oracle.

OracleServiceQAS
Start the database entering the command

Startup nomount;
Login to sql from the location where the control.sql file is located.
In our case, \oracle\QAS\sapbackup, Run

@control.sql
After the control file created, the Oracle is in Mounted state.

Select status from v$instance;
Execute,

Alter database open resetlogs;
Now dB is in open status.
Execute,

Select username from dba_users;
You can view the PRD OPS$ users
Now, copy ORADBUSR.SQL file from installation folder copy to sap backup directory and run.
You can find in C:\Program Files\sapinst_instdir\ERP\SYSTEM\ORA\CENTRAL\AS.
Execute the ORADBUSR.SQL file from the same location (\oracle\QAS\sapbackup\) from SQL

@ORADBUSR.SQL
Now, check again with the 10th step command.

Select username from dba_users;
Now, drop users of PRD system. Check again and confirm

Drop user <username>cascade;
Execute,

grant connect to “OPS$Hostname/SIDADM”;

grant sapdba to “OPS$Hostname/SAPSERVICESID;

grant dba to “OPS$Hostname/SIDADM”;

grant dba to “OPS$Hostname/SAPSERVICESID;

Post refresh activities:

Make the Batch Work Processes to zero (0). Set the parameter rdisp/wp_no_btc=0, so that no background job is trigger
Set the parameter rdisp/btctime=0, so that jobs are not picked up by the scheduler.
Start sap system and login with sap* user
Install SAP license
Delete/recreate TMS for target system using SE06
Configure SAP transport system (using STMS)
Import transports related to AL11, SE03, SMLG, RZ12, SM59, SALE and SM69 backup (which was done as part of pre-refresh steps)
Run transaction BDLS to change Logical System names.
Delete old SAP profiles and import new profiles using RZ10 transaction
Schedule only standard background jobs in SM36.
Schedule RDDIMPDP job.
Upgrade Kernel if required.
Perform mail configuration using SCOT transaction
Delete old mail related entries using SOST transaction.
Make necessary services active through SICF transaction
Execute SGEN transaction