Scribd
Upload
17 views

Duplicating Database

Uploaded by

bymash2007
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
17 views

Duplicating Database

Uploaded by

bymash2007
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 7

Overview of RMAN Database Duplication

Database duplication is the use of the DUPLICATE command to copy all or a subset of the
data in a source database. The duplicate database (the copied database) functions entirely
independently from the source database (the database being copied).

Purpose of Database Duplication.


A duplicate database is useful for a variety of purposes, most of which involve testing.
You can perform the following tasks in a duplicate database:
 Test backup and recovery procedures
For example, you can duplicate the production database on host1 to host2, and then use the
duplicate database on host2 to practice restoring and recovering this database while the
production database on host1 operates as usual.
 Test an upgrade to a new release of Oracle Database
 Test the effect of applications on database performance
 Create a standby database
You can create a physical standby database or an Oracle Data Guard far sync instance. A
standby database is a copy of the primary database that you update continually with archived
redo log files from the primary database. If the primary database is inaccessible, then you can
fail over to the standby database, which becomes the new primary database. A database copy,
however, cannot be used in this way: it is not intended for failover scenarios and
does not support the various standby recovery and failover options.
 Generate reports

Basic Concepts of Database Duplication


You must understand some basic concepts before duplicating a database.
The source host is the computer that hosts the source database. The source database
instance is the instance that is associated with the source database.
The destination host is the computer that hosts the duplicate database. The source host and
destination host can be the same or different computers.
For the duplication process, the database instance that is associated with the duplicate
database is called the auxiliary instance.
RMAN must perform database point-in-time recovery, even when no explicit point in time is
provided for duplication. Point-in-time recovery is required because the online redo log files
in the source database are not backed up and cannot be applied to the duplicate database. The
farthest point of recovery of the duplicate database is the most recent redo log file archived
by the source database.
RMAN assigns a new DBID to the duplicate database (except when a standby database is
created, in which case the source DBID is retained). You can then register the duplicate
database in the same recovery catalog as the source database.
If you copy a database with operating system utilities rather than the DUPLICATE command,
then the DBID of the copied database remains the same as the original database. To register
the copied database in the same recovery catalog with the original, you must change the
DBID with the DBNEWID utility.

Initialization Parameters for the Auxiliary Instance


Certain mandatory initialization parameters must be set for the auxiliary instance.
The following table describes a subset of the possible initialization parameters for the
auxiliary instance.

Initialization Parameter Value Status


DB_NAME The same name used in Required
the DUPLICATE command. If you use
the DUPLICATE command to create
a standby database, then the
name must be the same as the
primary database.
The DB_NAME initialization parameter
for the duplicate database must be
unique among databases in its Oracle
home.

CONTROL_FILES Control file locations . Required

DB_BLOCK_SIZE The block size for the duplicate Required,


database. This block size must if this
match the block size of the source initializati
database. If the source database on
parameter
parameter file contains a value for
is set in
the DB_BLOCK_SIZE initialization the source
parameter, then you must specify database
the same value for the auxiliary
instance. However, if
no DB_BLOCK_SIZE parameter is
specified in the source database
initialization parameter file, then
do not
specify DB_BLOCK_SIZE parameter in
the auxiliary instance.

DB_FILE_NAME_CONVERT Pairs of strings for converting the Optional


names of data files and temp files.
You can also
specify DB_FILE_NAME_CONVERT para
meter on the DUPLICATE command
itself. See "Using the
DB_FILE_NAME_CONVERT
Parameter to Generate Names for
Non-OMF or ASM Data Files".

LOG_FILE_NAME_CONVERT Pairs of strings for naming online Optional


redo log files. See "Using the
LOG_FILE_NAME_CONVERT
Parameter to Generate Names for
Non-OMF or ASM Log Files".

DB_CREATE_FILE_DEST Location for Oracle managed data Optional


files.

DB_CREATE_ONLINE_LOG_DE Location for Oracle managed Optional


ST_n online redo log files.

DB_RECOVERY_FILE_DEST Location for fast recovery area. Optional

You might also like