HOMOGENEOUS / HETEROGENEOUS / DB REFRESH PROCEDURE IN

INTERVIEW PATRON POST & PRE STEPS

8:08 AM sapdatabase v 4 comments

SYSTEM COPY. HOMOGENEOUS/HETEROGENEOUS/DB REFRESH.

System copy is a process of setting up a new system using a copy/backup of existing
system.
It is required in the following scenarios.

I.
H/w migration.
II.
Os/db migration.
III.
Testing the backup of sap system.
IV.
Patch application and kernel upgrade.
V.
Sap upgrade.
VI.
To test the developed objects before moving to production.
VII.
To setup a sandbox, testing of training system in the landscape.
There are various ways to perform a system copy.
Homogeneous system copy- if there is no change in the database of operating system.
Homogeneous system copy can be performed by following methods.
1. File system copy.
2. Database backup and restore (db specific method).
3. Sapinst tool export and import.
Note: option 3 is the only method for heterogeneous copies/Unicode conversions, net weavers
system based on java. For heterogeneous system based on oracle and db2. Sap also supports db
specific methods using br tools.
Heterogeneous system copy- if there is a change either in the os or db of the target system. It has to
be performed by a os/db migration certified consultant.
If the system is setup as new system then it is referred as system copy/installation os, db,
erp, restore/import is required for which no [re steps are required i.e the system is
completely built from os, db and r/3 without changing os or db.
DB REFRESH:
The system exists with os, db, erp (sap component). Which is refreshed (replaced) by the
database of any other system mostly PRD in the landscape. In such cases the source
dependencies need to be documented or transported to revert them back after the refresh.
HOMOGENEOUS SYSTEM COPY(FILE SYSTEM COPY)
1. Take full offline backup of database using BR Tolls/DB 13.
Directly using the single line command of brtools
Brbackup u p init<sid>.sap d disk t offline m all
or go through the br tools menu
Select 4th option backup and database copy
Select 1st option database backup
Select 2nd to change backup device type to disk
Select 6th to change backup type to offline_force type c for continue

Select 3rd option of menu for compression mode and set to yes. And the backup starts and in b/w
asks for prompt continue, then type c to continue.
2. Generate of control file.
By generating trace file at os level (this method is used for /DB refresh )
Sql> alter database backup controlfile to trace
We can find the trace file in oracle/sid/saptrace/usertrace. Copy it on the desktop and do the
modifications.
Remove all the lines above STARTUP NOMOUNT below CHARACTER SER UTF8; save
the file.
Replace S_sid with T_sid.
Replace REUSE with SET.e
Replace NORESETLOGS with RESETLOGS.
Replace ARCHIVELOG with NOARCHIVELOG.
Copy the init<sid>.ora and init<sid>.sap from source system(oracle/sid/102/database) and
change the source S_sid with T_sid.
By using ORABRCOPY tool (java tool to generate control file)
ORABRCOPY is available as .SAR file in instmaster/im_windows_i386/common/dbtools/install
/ora
Create a new directory copy the .sar file full permission, login to <Sid>adm and uncar using the
command SAPCAR XVF ORABRCOPY.SAP
It will generate 3 files
1. Ora_br_copy.sh ------- used for linux os.
2. Ora_br_copy.bat -------used for windows os.
3. Orabrcopy .jar.
Now generate the control file using (orasid)
Ora_br_copy.bat -generateFiles forceLogSwitch targetSid < **> -password <******>
-listnerPort 1521
It will generate control.sql(target system) and control.trc(source system) and init<sid>.ora (target
system).
Compare control.sql with control.trc and change according to control.trc file in control.sql file.
Copy the init<sid>.sap from /oracle/sid/102/database of the source system and change S_sid with
T_sid.
3. Target system preparation
Install os and oracle with same patch level as source.
Go to installation master and run Sapinst and select as below
Sap net wear 2004s support release.
Sap system.
Additional life cycle tasks.
System copy.
Oracle.
Target system.
Central instance as abap.
Click ok.
Select the custom option. It will ask for log off click ok.
Select the java component.

Select the jdk directory.

Select the jce policy archive.
Provide sap sid .<T01>
Installation drive<e:>.
Enable Unicode system.
Provide the password.
Select local installation.
Provide os user password.
Select homogeneous system copy.
Provide db sid. it will show a reference error
Go to installation directory (pf/sap_instdir/nw045/lm/copy/ora/system/central/as/edit control.xml.
Search for update ORACHECK_PAR
and delete line row. Create Db= false and restart
the installation.
Provide the DB system parameters.
Select the DB system driver for installation
Provide standard database users
Click next for 4 times
Select kernel and oracle client path
Now it will ask to restore the db data. Click ok
Copy the init<dbsid>.sap from source system. Replace S_sid with T_sid and place it in target
system /oracle/sid/102/database directory.
Copy the init<dbsid>.ora from source system and replace S_sid with T_sid and place database
directory.
Copy control.sql file and place it in the target system installation directory.
Change S_sid with T_sid in b*****.afd log file which is generated during the offline backup.
Create the folders mirrlogA, mirrlogB, oraarch, saparch, origlogA/cntrl, origlogB/cntrl,
sapbackup. Sapcheck, sapdata1/cntrl, sapdata2, sapdata3, sapdata4, sapreorg,
saptrace/background and usertrace.
Copy the backup of source system and keep in the target system sapbackup directory.
Switch the user <sid>adm and restore the db using
brrestore u b b*****.afd d disk k yes m all
-k denotes compress mode
-d means device type
-b backup log file
Click ok to continue and the target system installation will complete itself.
To ensure that the system copy is done successfully or not. We have to calculate the count of the
tables before and after the system copy
RSTABLESEZE, TADIR, DD02L, TFDIR, TSTC, patch level, tables related to material master
(MARA), vendor master (LFA1), plants and storage locations (T001l),RFCDES for RFC
connections.
RSTABLESIZE is the report used to find the size of client patch level (ABAP,BASIS,APPL &
HR) screen shots.