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…

Question

Options

• Aby using the RMAN switch command to set the new location for the data files
• Bby using the RMAN duplicate command with nofilenamecheck to recover the database to the
• Cby using the RMAN duplicate command with dbid and set new name for tablespace to recover
• Dby creating a new database in the new host, and then using the RMAN recover command

• A
  6% (2)
• B
  76% (26)
• C
  15% (5)
• D
  3% (1)

Explanation

Option B is correct because RMAN DUPLICATE is the purpose-built command for creating a copy of a database from existing backups, and the NOFILENAMECHECK clause is required specifically when the duplicate host uses the same directory structure as the source - RMAN would otherwise refuse, thinking the files conflict. Since the production database is open and backups exist in the recovery catalog, RMAN can duplicate from those backups without taking production offline, and the new database can subsequently be registered and used with that same catalog.

A is wrong - SWITCH simply redirects RMAN's pointer to a datafile's new physical location after a manual move; it has nothing to do with creating a duplicate database.

C is wrong - specifying DBID would target the existing production entry in the catalog (causing a conflict), and SET NEW NAME FOR TABLESPACE is only needed when the directory structure differs between source and target - the opposite of this scenario.

D is wrong - RECOVER restores an already-existing database after a failure; it cannot bootstrap a brand-new duplicate from scratch the way DUPLICATE can.

Memory tip: Associate DUPLICATE … NOFILENAMECHECK with the phrase "same path, different place" - same directory structure, different host, so no filename conflict check is needed.

No community discussion yet for this question.