Your production database is running in archivelog mode. You use RMAN with a recovery
catalog to back up your database to media and the database is uniquely identified in the
recovery catalog. You want to create a test database from the production database and
allow the production database to remain open during the duplicate process. You restore the
database backups to a new host with the same directory structure as the production
database and want to use the recovery catalog for future backups after the database is
successfully restored to the new host. How would you achieve this?
A.
by using the RMAN duplicate command with nofilenamecheck to recover the database to
the new host
B.
by using the RMAN duplicate command with dbid and set nekname for tablespace to
recover the database to the new host
C.
by creating a new database in the new host, and then using the RMAN recover
command
D.
by using the RMAN switch command to set the new location for the data files
Explanation:
wrong for sure is C recover => keeps the DBID and therefore not feasible!
I think but not sure that the right answer is “Please verify”:
by using the RMAN duplicate command with nofilenamecheck to recover the database to the
new host.
A
A