System Refresh

System refresh is nothing but moving the production system data to quality system for testing purpose.

Generally system refresh will be done when the client size is more and we cannot move the production system data to quality system.

Types of system refresh:-

1.  Using offline backup

2.  Using online backup

Procedure:-

Source system (Production)

1.  Take the screenshots of important T-code

Ex: SCC4, SM58, ST06, SM36, SM37 and the clients specified t-cods.

2.  Export client settings – Table T000

3.  Printer settings – Table TSP03 and TSP03C

OR

In SPAD t-code we can export or import and delete the configuration

4.  RFC Destination – Table RFCDES

Note: - For all the above we have to create the DUMY transport request in t-code SE01.

5.  Apart from this we also take the backup of user master record. For this we will export SAP_USR profile in SCC8 t-code.

6.  For all the transport requests we have to take down the transport number.

7.  Take the clean offline backup (Will be done by backup team)

8.  Generate the control file using the command

Alter database backup controlfile to trace

File will be stored in path- oracle/SID/saptrace/usetrace

9.  Edit the control file as mentioned below

a.   Delete above startup nomount

b.  Delete below character set UTFS ;

c.   Replace Reuse to SET – Will change Source SID to Target SID.

d.  Replace No Resetlog to Resetlog – Will change the log sequence of offline redolog files

e.   Replace Archiving to No Archiving – Will avoid creating log files while starting the system

10.              Save the control file as .sql or .trc.

Target system (Quality)

1.  Delete all contents inside

Sapdata1, sapdata2 to sapdataN, origlog A, origlogB, MirrorlogA, MirrorlogB, saptrace, sapreorg, sapcheck

Command to delete – rm –rf sapdata*

2.  Ask backup team to restore the source system backup to target system

Note: If we have root access no problem, if it is not there UNIX team will change root permission.

    Command is chown –r

        

         Change the permission inside root

            Command – chown –r datafile name

3.  Run the script – DB will come to nomount state

4.  Then recover the database using the command

Recover database using controlfile untill cancel

5.  Execute command

Alter database open resetlog – It will reset redolog sequence number

6.  Then execute command – shutdown immidate

7.  Execute startup – will start oracle

8.  Change the OPS$ password – Through BRTOOLS – BRCONNECT – 8, 4

9.  Make background process Zero

Rdisp/wp_no_btc=0

10.      Startup – Will start SAP

Post activity:

1.  Import RFC definition, client settings, printer settings, Delete and configure SMQ1 and SMQ2

2.  Change the background parameter

3.  Restart the system

If we are using online backup then we have do below mentioned steps.

1.  Perform point-in recovery

2.  To do point-in recovery we have to copy the orccrch directory from source system to target system.

Command - Recover database using controlfile untill time and date.

After refresh if the system is not starting do the below steps.

1.  Check R/3 trans is working or not

Command- R3trans –d – It will check the connection between SAP and DB

2.  Delete source system OPS$ password

3.  Change OPS$ password through BRCONNECT option 8, 4

Note: SQL file character will be changed in init.ora file

    Path: oracle/SID/102_64/dbs/init.ora

            oracle/SID/102_64/dbs/init.sap