Your database is running on the host OUSERVER. You back up your database regularly using RMAN and the backups are cataloged in a recovery catalog. For testing purposes, you want to replicate your database to another host, OUSERVER1, with the same directory structure. So, you copy the backups to the new host.
What must you do to make the database operational in OUSERVER1?
A.
Restore the control file from the backup by using the CATALOG option, restore the data files by using the SET NEWNAME command, and recover the data files.
B.
Restore the data files by using the NOCATALOG option and use the SET NEWNAME command to change the location.
C.
Restore the control file from the backup by using the NOCATALOG option, and then restore and recover the data files.
D.
Restore the data files from the backup by using the recovery catalog, use the SWITCH command to change the location, and recover the data files.
D
Oracle provides the SWITCH command to use in place of the RESTORE command. This will essentially change the control file so it will point to the data file copy(ies). You then would call the RECOVER command to apply any incremental backups and archived redo logs to restore the data file(s) or tablespace(s).
If RMAN is connected to a recovery catalog, and if the database is using a control file restored from backup, then SWITCH updates the control file with records of any datafiles known to the recovery catalog but missing from the control file
Wouldn’t C is adequate? ‘with the same directory structure’ means not need for Set Newname or Switch?
JJ is correct. SWITCH is not needed:
A SWITCH is equivalent to the SQL statement ALTER DATABASE RENAME FILE: the names of the files in the RMAN repository are updated, but the database does not rename the files at the operating system level.
C
C, because the same directory structure is applied to new DB, so no need to use ‘SET NEWNAME’ to set a new path.