289.You are managing the APPPROD database as a DBA which is not using the Oracle-managed files.
You plan to duplicate this database in the same system with the name DUPDB.You want to create the
same directory structure for duplicate database files as of the target database.
You executed the following RMAN commands:
RMAN> CONNECT TARGET sys/sys@APPPROD
RMAN> CONNECT AUXILIARY sys/sys@DUPDB
RMAN> DUPLICATE TARGET DATABASE
TO dupdb
FROM ACTIVE DATABASE
PASSWORD FILE
SPILE
NOFILENAMECHECK;
What are the implications of this command?
A. It creates database files for the duplicate database under the Oracle base with a different directory for
the duplicate database.
B. It overwrites data files of the target database because a different location for data files is not mentioned
for the duplicate database.
C. It creates database files for the duplicate database under the same Oracle home as that of the target
database with the same directory structure.
D. It creates database files for the duplicate database under the same Oracle home as that of the target
but with a different directory for the duplicate database.
Answer: B
答案解析：
官方参考：http://docs.oracle.com/cd/E11882_01/backup.112/e10643/rcmsynta020.htm#RCMRF90163
NOFILENAMECHECK |
Prevents RMAN from checking whether the data files and online redo logs files of the source database are in use when the source database files share the same names as the duplicate database files. You are responsible
for determining that the duplicate operation does not overwrite useful data.
This option is necessary when you are creating a duplicate database in a different host that has the same disk configuration, directory structure, and file names as the host of the source database. For example, assume that you have a small database located
in the /dbs directory of srchost:
/oracle/dbs/system_prod1.dbf
/oracle/dbs/users_prod1.dbf
/oracle/dbs/rbs_prod1.dbf
Assume that you want to duplicate this database to desthost, which has the same file system/oracle/dbs/*, and you want to use the same file names in the duplicate database as in the source database. In this case, specify
the NOFILENAMECHECK option to avoid an error message. Because RMAN is not aware of the different hosts, RMAN cannot determine automatically that it should not check the file names.
If duplicating a database on the same host as the source database, then ensure that NOFILENAMECHECK is not set. Otherwise, RMAN can potentially overwrite and corrupt the target database data files, temp
files, or online logs. It may also signal the following error:
RMAN-10035:
exception raised in RPC:
ORA-19504: failed to create
file "/oracle/dbs/tbs_01.f"
ORA-27086: skgfglk: unable to lock file - already in use
SVR4 Error: 11: Resource temporarily unavailable
Additional information: 8
RMAN-10031: ORA-19624 occurred during call to
DBMS_BACKUP_RESTORE.RESTOREBACKUPPIECE
|