Beruflich Dokumente
Kultur Dokumente
SAP recommends that you make a system copy in order to build a test,
demo, training or standby system (Oracle and Informix: standby systems
cannot be created with a system copy). You should perform upgrades in a
test system first. This way you can identify customer pecific problems which
might result from modifications. Thus, we can sort the general needs for a
system copy as follow:
If The system copy takes place between systems with different platforms ( at
least one of the component must be different, OS or RDBMS ), we call this
HETEROGENEOUS SYSTEM COPY.
Prerequisites
Following conditions must be provided to copy a system:
a. Both Source and Target Systems must have Same Operating System
and Database System. Also Patch levels must be same.
b. You have sufficient free space for sapdata directories on target system.
c. For Windows systems, you have to create all drives where datafiles
resides on source system.
d. Use most current database backup in order to shorten database
creation time.
Procedure
1. Data and Log directories on target system must be cleaned before
restoring source database. Here below are the commands to clean
directories. Before this, you have to stop all SAP and Oracle processes.
back.log File
Copy this detailed backup log file into /oracle//sapbackup directory on target
system. Use BRRESTORE command below to restore the source database on
target system. You can also restore datafiles and online redolog files (if you
are using offline backup) using backup tools such as BACKFM tool of IBM
TSM.
3.a. Mount the necessary backup volume on target system.
At the first step of restore, system will recognize that the Oracle SID is
different on target machine (where the restore command executed) and in
backup. Also, Oracle_Home parameters in backup and in current system will
be different and recognized by brrestore. But the restore command will
restore the datafiles to match current systems file system. Here is a sample
log of a restore.
All the datafiles and online redolog files (only for Offline DB Backup) must be
successfully restored.
At this step, there are 3 probability that must be take into account for the
following steps.
You are using an online database backup of source system to create target
system.
You have to find and put all archive files created during online backup into
target systems archive directory to be able to recover database. You can
also apply all the archives created from the online backup start time to latest
available.
You are using an offline database backup of source system which is running
in ARCHIVELOG mode to create target system.
You may find the archive files created after offline backup on source system
to make database current on target system via applying during recovery.
You are using an offline database backup of source system which is running
in NOARCHIVELOG mode to create target system.
You don't have any archive files created on source system so you don't need
anything.
You have to edit this file to be able to use for CONTROLFILE creation on
target system.
as follow
If you want to change datafile or redolog file destinations, first move the
files on target destination at OS level, then edit CONTROL.SQL file for new
destinations.
5. After CONTROL.SQL script preparation, following commands must be run
to create CONTROLFILE of target system:
# su – ora
SVRMGR> alter database open; alter database open * ORA-01589: must use
RESETLOGS or NORESETLOGS option for database open SVRMGR> alter
database open resetlogs; alter database open resetlogs * ORA-01195: online
backup of file 1 needs more recovery to be consistent ORA-01110: data file
1: '/oracle//sapdata1/system_1/system.data1'
7.a. If your source system is runnig in NOARCHIVELOG mode, then you have
to use the following command to recover database.
7.b. If you restored an online backup on target system and put all the archive
files created since online backup start time, use the following commands.
After execution of this command, Oracle will ask for archive files to be
consistent. As archive files contains only database changes commands, you
will use source system archive file on new systems database recovery. Copy
all archive files created since online backup on source system to archive
directory of target system. Archive file names are different from asked
during recovery session. You can change archive file names for target
system via the following script.
After application of all necessary archives (at least all the archives created
during online backup must be applied. Archives from this point can be
applied to make database current), next request for archive is cancelled via
CANCEL command.
But recovery session must be started with the following command and
cancelled again to ba able to start database.
7.c. If you restored an offline backup on target system, you can recover
database to the time of backup completed or you can recover database to
the most current status using archive files. The archive application and
statup of database is same as an online backed up database copy in "7.b".
# su -adm # startsap
1. As your Hardware Key is not changed, you don't have to get additional
License Key from SAPNET. You can use previous systems (on target
system, if SID is not changed) License in new system created on target
system.
2. Logon to the SAP R/3 System and goto TCODE SE06. Select "Database
Copy or Migration" and execute "Post Installation Processing".
SE06
Change all of the Source System Objects to Target System Objects as asked.
1. Delete old TMS configuration and make new configuration for TMS via
STMS TCODE.
2. After all of above steps, you have completed a System Copy using
Online/Offline Database Backup.