Which two operations are NOT performed by the DUPLICATE command in Recovery
Manager (RMAN) while duplicating a running database? (Choose Two)
A.
Creating the control file for the duplicate database
B.
Restoring the target data files to the duplicate database
C.
Performing complete recovery using all available backups
D.
Generating a new, unique DBID for the duplicate database
E.
Copying the online redo log files from the target database to the duplicate database
Answer C and E is correct because …
as can be seen in …
http://oracle.su/docs/11g/backup.112/e10642/rcmdupdb.htm#CHDJJBCF
Just under the title “How RMAN Duplicates a Database” it says …
RMAN must perform database point-in-time recovery, even when no explicit point in time is provided for duplication. Point-in-time recover 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.
B and E are correct.
From Eamon link:
“In active database duplication, RMAN connects as TARGET to the source database instance and as AUXILIARY to the auxiliary instance. RMAN copies the live source database over the network to the auxiliary instance, thereby creating the duplicate database. No backups of the source database are required.”
C and E because:
As part of the duplicating operation, RMAN automates the following steps:
1:Creates a default server parameter file for the auxiliary instance if the following conditions are true:
a. Duplication does not involve a standby database.
b.Server parameter files are not being duplicated.
c.The auxiliary instance was not started with a server parameter file.
2:Restores from backup or copies from active database the latest control file that satisfies the UNTIL clause requirements.
3:Mounts the restored or copied backup control file from the active database.
4:Uses the RMAN repository to select the backups for restoring the datafiles to the auxiliary instance. This step applies to backup-based duplication. (ANSWER B)
5:Restores and copies the duplicate datafiles and recovers them with incremental backups and archived redo log files to a non-current point in time.
6:Shuts down and restarts the database instance in NOMOUNT mode.
Creates a new control file, which then creates and stores the new DBID in the datafiles. (ANSWER A)(ANSWER D)
Opens the duplicate database with the RESETLOGS option and creates the online redo log for the new database.
[..]
the online redo log files in the source database are not backed up (ANSWER E) 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. (ANSWER C)