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 switch command to set the new location for the data files
B.
by using the RMAN duplicate command with nofilenamecheck to recover the database to the new host
C.
by using the RMAN duplicate command with dbid and set nekname for tablespace to recover the database to the new host
D.
by creating a new database in the new host, and then using the RMAN recover command
ANS B?
B
B
You create a duplicate database by using the RMAN DUPLICATE command. The duplicate database is the copied database, whereas the source database is the database that you are copying. The duplicate database has a different DBID from the source database and functions entirely independently. The source host is the computer that hosts the source database, whereas the destination host is the computer that hosts the duplicate database.
ยท NOFILENAMECHECK
Prevents RMAN from checking whether the source database datafiles and online redo logs files share the same names as the duplicated files. This option is necessary when you are creating a duplicate database in a different host that has the same disk configuration, directory structure, and filenames as the host of the source database.
As part of the duplicating operation, RMAN automates the following steps:
-Generates a new, unique DBID for the duplicate database
http://www.aiotestking.com/oracle/how-would-you-achieve-this-19/
The NOFILENAMECHECK option is specified because it is necessary when the duplicate database files use the same names as the source database files.
The DUPLICATE command automatically assigns the duplicate database a different DBID so that it can be registered in the same recovery catalog as the source database.
A standby database, unlike a duplicate database created by DUPLICATE without the FOR STANDBY OPTION, does not get a new DBID.
https://docs.oracle.com/database/121/BRADV/rcmdupdb.htm#BRADV89929
https://docs.oracle.com/database/121/SBYDB/rcmbackp.htm#SBYDB4981