Database Cloning using RMAN with Backup based Duplication on the Local Host Introduction Use the DUPLICATE command to create a copy of a source database. RMAN can create either of the following types of databases: A duplicate database, which is a copy of the source database (or a subset of the source database) with a unique DBID. Because a duplicate database has a unique DBID, it is independent of the source database and can be registered in the same recovery catalog. Typically, duplicate databases are used for testing. A standby database, which is a special copy of the source database (called a primary database in a Data Guard environment) that is updated by applying archived redo log files from the primary database. A standby database is not assigned a new DBID. Prerequisites 1. Backup should be taken. 2. RMAN must be connected as TARGET to the source database, which is the database that is being copied. The source database must be mounted or open. The source database must not be a standby database. 3. RMAN must be connected as AUXILIARY to the instance of the duplicate database. The instance of the duplicate database is called the auxiliary instance. The auxiliary instance must be started with the NOMOUNT option. Prerequisites Specific to Backup-Based Duplication 1. When you execute DUPLICATE without FROM ACTIVE DATABASE, at least one auxiliary channel is required, but no normal channels are required in the source database. 2. When you duplicate the database from backups, all backups and archived redo logs used for creating and recovering the duplicate database must be accessible by the server session on the destination host. If the destination host is not the same as the source host, then you must make backups on disk on the source host available to the destination host with the same full path name as in the source database. RMAN can perform the duplication in any of the following supported modes: 1. Active duplication 2. RMAN duplicates the files directly from either an open or mounted database. 3. Backup-based duplication without a target connection
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Database Cloning using RMAN with Backup based
Duplication on the Local Host
Introduction
Use the DUPLICATE command to create a copy of a source database. RMAN can create either of the
following types of databases:
A duplicate database, which is a copy of the source database (or a subset of the source database) with
a unique DBID. Because a duplicate database has a unique DBID, it is independent of the source
database and can be registered in the same recovery catalog. Typically, duplicate databases are used for
testing.
A standby database, which is a special copy of the source database (called a primary database in a
Data Guard environment) that is updated by applying archived redo log files from the primary database.
A standby database is not assigned a new DBID.
Prerequisites
1. Backup should be taken.
2. RMAN must be connected as TARGET to the source database, which is the database that is being
copied. The source database must be mounted or open. The source database must not be a
standby database.
3. RMAN must be connected as AUXILIARY to the instance of the duplicate database. The instance
of the duplicate database is called the auxiliary instance. The auxiliary instance must be started
with the NOMOUNT option.
Prerequisites Specific to Backup-Based Duplication
1. When you execute DUPLICATE without FROM ACTIVE DATABASE, at least one auxiliary channel
is required, but no normal channels are required in the source database.
2. When you duplicate the database from backups, all backups and archived redo logs used for
creating and recovering the duplicate database must be accessible by the server session on the
destination host. If the destination host is not the same as the source host, then you must make
backups on disk on the source host available to the destination host with the same full path
name as in the source database.
RMAN can perform the duplication in any of the following supported modes:
1. Active duplication
2. RMAN duplicates the files directly from either an open or mounted database.
3. Backup-based duplication without a target connection
4. RMAN creates duplicate files from pre-existing RMAN backups and copies. The DUPLICATE
command must have been issued with the DATABASE clause. This form requires a connection to
an auxiliary instance and a recovery catalog.
5. This mode is useful when the target database is not available or a connection to it is not
desirable (as mandated by security policy restrictions or a firewall).
6. Backup-based duplication with a target connection.
7. RMAN creates duplicate files from pre-existing RMAN backups and copies.
8. Backup-based duplication without connection to target and recovery catalog
9. RMAN creates duplicate files from RMAN backups and copies that were placed in a designated
BACKUP LOCATION.
Procedure
1. Create Listener for the Database and add the entry of the following