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
shit, this answer have a wrong organization.
B
Does anyone have a correct answer for this one? Is it D orB?
I would say B is the answer.
https://docs.oracle.com/database/121/BRADV/rcmdupdb.htm#BRADV538
it says it will use same directory structure, do we need to say switch command?
I think tricky point is he wants to use recovery catalog, it is possible to register 2 database with same dbid?
“You can only register a target database with a DBID that is unique within the recovery catalog. Databases with the same name are permitted if the DBID values are different. The database that you are registering must not be a standby database.
“
i would say C
Answer is B – if not used with FOR STANDBY then DUPLICATE changes DBID implicitly.
The question is:
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?
Anh all answers seem not to have any relevance.
B
https://docs.oracle.com/cd/B28359_01/backup.111/b28270/rcmdupdb.htm#CHDGFABD
Hello All,
The answer is indeed “D”. Please read these lines in the question
“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”
The Test DB server has the files already restored so all we have to do is to recover the test DB without using the catalog but by using RMAN recover commands.
The author means by future backups is, the backups of Prod and not of Test.
So I am confident the answer is D.
Not B, why to use Duplicate if the file are already restored.
Hope this helps, Suggestions are welcome
When duplicating a database, RMAN generates names for the duplicate database files. If the destination host uses the same directory structure as the source host, then you can use the same names for the duplicate database files that you used for the source database files. In this case, you do not need to rename the duplicate files, but you do have to specify the NOFILENAMECHECK option on the DUPLICATE command.
So I would say: 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
Thanks Goszczu
B