Restoring Database PRD to QAS homogenous

April 21, 2011 at 2:42 pm Leave a comment


In quality all the file systems must be in same size as production system

After installation of SAP in quality

Take the offline / online backup of production system using db13

Connect the tape drive / backup drive to quality system

Check the drive using: brbackup –I show –n  1

Copy the backup log file from prod to quality

Eg: in prod

/oracle/<sid>/sapbackup/abcd.afp file

To QAS

/oracle/<sid>/sapbackup/abcd.afp

&

Copy  back<sid>.log file from production quality to /oracle/<sid>/sapbackup/backsid.log

Modify the .afp file from old sid to new sid eg: HPS to HQS except at volume_backup, Following backup volume will be used, Volume with name HPSB15 required in device.

In quality system run the following command in orasid user name

brrestore –b  <modified backuplogfile> -m FULL

After completion of restoring generate control file in production system using

Sqlplus “/as sysdba”

Sql> ALTER DATABASE BACKUP CONTROLFILE TO TRACE;

Copy that trace file from production /oracle/sid/saptrace/usertrace/*.trc (latest file) to qulity

Modify the trace file

Delete the lines before STARTUP NOMOUNT and after CHARACTER SET UTF8;

And modify old <sid> to new <sid> in all the lines

Modify the line after startup nomount as

CREATE CONTROLFILE SET DATABASE “SID” RESETLOGS FORCE LOGGING ARCHIVELOG

Rename the file to contrl.sql and place it in /oracle/sid/saptrace/usertrace/

Rename the cntrlsid.dbf files to old_cntrlsid.dbf in the following locations in quality

/oracle/sid/sapdata1/cntrl/

/oracle/sid/origlogA/cntrl/

/oracle/sid/origlogB/cntrl/

Any other places with cntrl folder

Run the contrl.sql from /oracle/sid/saptrace/usertrace

Sqlplus “/as sysdba”

Sql> shutdown immediate;

Sql> @contrl.sql

After successful creation of control file.

Sql> ALTER DATABASE OPEN RESETLOGS;

Now database must be in open

You need to create the users

OPS$ORA<newsid>

OPS$SAPSERVICE<newsid>

OPS$<newsid>ADM in database with same authorizations of old sid users.

Now check the connectivity using r3trans –d if successful you can start sap.

Note: It works only in homogenous environments if  its heterogeneous then use systemcopy method

Entry filed under: Uncategorized.

steps for online/offline backup oracle-sap BI Transports source system issue

Leave a comment

Trackback this post  |  Subscribe to the comments via RSS Feed


Calendar

April 2011
M T W T F S S
 123
45678910
11121314151617
18192021222324
252627282930  

Most Recent Posts