Creating and updating duplicate databases with rman oc dating
The destination host must have access to the RMAN backups required to create the duplicate database. These channels correspond to a server session on the auxiliary instance on the destination host.
For active database duplication, the type of duplication technique used determines which channel performs the principal work.
The farthest point of recovery of the duplicate database is the most recent redo log file archived by the source database.
As part of the duplicating operation, RMAN automates the following steps: Before duplicating the database, you must decide how to perform the duplication and then prepare the database environment, including the auxiliary database instance.
connections to the target or to the recovery catalog database instance.
RMAN connects to the auxiliary instance of the duplicate database on the destination host.
Release 1 (12.1), RMAN can use backup sets to transfer the source database files that need to be duplicated.
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.
When active database duplication is performed using backup sets, the principal work of duplication is performed by the auxiliary channels.
When image copies are used, the primary work is performed by the target channels.