Duplication with Oracle Managed Files
If the source database files are in the Oracle Managed Files (OMF) format, then you cannot use the DB_FILE_NAME_CONVERT
andLOG_FILE_NAME_CONVERT
initialization parameters or the fileNameConversionSpec
clause to generate new OMF file names for the duplicate database. If you do not follow this rule, the new OMF files generated from these three methods can cause problems. For more information on OMF names, see the "Considerations When Renaming OMF Auxiliary Set Files in TSPITR" in the Oracle Database Backup and Recovery User's Guide
//如果源库使用OMF,那么duplicate过程中不能使用db_file_name_convert和log_file_name_convert
The only exception to this rule is when changing only an ASM disk group name. Assume that source data files and online redo log files are stored in ASM disk group +SOURCEDSK
. You want to store the duplicate database files in ASM disk group +DUPDSK
. In this case, you can set the initialization parameters as follows:
DB_FILE_NAME_CONVERT = ("+SOURCEDSK","+DUPDSK") LOG_FILE_NAME_CONVERT = ("+SOURCEDSK","+DUPDSK")
RMAN uses DB_FILE_NAME_CONVERT
or LOG_FILE_NAME_CONVERT
to convert the disk group name, and then generates a new, valid file name based on the converted disk group name.
You have the following other supported options for naming data files when the source files are in the Oracle Managed Files format:
-
Use
SET
NEWNAME
to specify names for individual data files.
//使用SET NAME -
Set
DB_FILE_CREATE_DEST
to make all data files of the new database Oracle-managed files, except the files for whichSET NEWNAME
is used. You should not setDB_FILE_NAME_CONVERT
if you setDB_FILE_CREATE_DEST
.
//使用DB_FILE_CREATE_DEST
Supported options for naming online redo logs duplicated from Oracle-managed files are DB_CREATE_FILE_DEST
, DB_RECOVERY_FILE_DEST
, orDB_CREATE_ONLINE_LOG_DEST_
n
.
//DB_CREATE_ONLINE_LOG_DEST_
n
(where n
= 1, 2, 3, ... 5) specifies the default location for Oracle-managed control files and online redo logs.