Backing Up Oracle - Computing at Cornell

As part of the duplication operation, RMAN manages the following:
Restores the target datafiles into the duplicate database and performs
incomplete recovery using all available archived redo logs and
incremental backups.
Opens the duplicate database with the RESETLOGS option after incomplete
recovery to create the online redo logs.
Generates a new, unique database identifier for the duplicate database.
When duplicating a database, you can do the following:
Skip read-only tablespaces with the skip readonly clause. Read-only
tablespaces are included by default. If you omit them, you can add them
later.
Create your duplicate database in a new host. If the directory structure is
the same on the new host, you can use the nofilenamecheck option and
reuse the target datafile filenames for the duplicate datafiles.
Use the set until option when creating the duplicate database to recover
it to a non-current time. By default, the duplicate command creates the
database using the most recent backups of the target database and then
performs recovery to the most recent consistent point contained in the
incremental backups and archived redo logs.
Use the duplicate command without a recovery catalog.
Register the duplicate database in the same recovery catalog as the target
database. This option is possible because the duplicate database receives
a new database identifier during duplication. If you copy the target
database using operating system utilities, the database identifier of the
copied database remains the same so you cannot register it in the same
recovery catalog.
In our test environment, we duplicated the database oslo to the database
berlin. Both databases are located on the same AIX system.
We performed the following steps:
We created an Oracle password file for the new instance berlin:
cd $ORACLE_HOME/dbs
orapwd file=orapwberlin password=change_on_install entries=10
Chapter 8. Recovering Oracle Databases on UNIX 115