Some important knowledge points about rman duplicate-Series 3, rmanduplicate

Some important knowledge points about rman duplicate-Series 3, rmanduplicate

FYI:

Http://docs.oracle.com/cd/E11882_01/backup.112/e10643/rcmsynta020.htm#RCMRF126

Rman duplicate database must be on the same platform, but 32bit \ 64bit replication is supported. After the replication is complete, run ￥ ORACLE_HOME/rdbms/admin/utlirp. SQL.
Script to convert pl/SQL code


The DUPLICATE command requires one or more auxiliary channels. These channels perform the work of the duplication on the auxiliary database instance.
The rman duplicate Command requires at least one auxiliary channel (aupoliciary channels) to be allocated to the slave database)


If the source database files are in the Oracle Managed Files (OMF) format, then you cannot use the DB_FILE_NAME_CONVERT and
LOG_FILE_NAME_CONVERT initialization parameters or the fileNameConversionSpec clause to generate new OMF file names for
Duplicate database. If you do not follow this rule, the new OMF files generated from these three methods can cause problems
When using duplicate, you must note that if the source database uses OMF, you cannot use DB_FILE_NAME_CONVERT, LOG_FILE_NAME_CONVERT, or other files for conversion.
Otherwise, a problem occurs. For example, the data file name in the control file of the standby database is converted according to DB_FILE_NAME_CONVERT and LOG_FILE_NAME_CONVERT, but the actual

If the data file is not located in the corresponding path, the actual file will be managed using OMF. In this case, you need to use:

1. RMAN catalog and switch database to copy

2 alter database rename file to and

3. switch datafile file # to copy to modify the control file information;

Of course, there are exceptions. If you only change the names of the asm disk group and the other path names remain the same, you can use DB_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.


-If the source database uses OMF, the following parameter configurations are recommended:
You have the following other supported options for naming data files when the source files are in the Oracle Managed Files format:

1. Use set newname to specify names for individual data files.
2. Set DB_FILE_CREATE_DEST to make all data files of the new database Oracle-managed files, cannot the files for which SET


NEWNAME is used. You shocould not set DB_FILE_NAME_CONVERT if you set DB_FILE_CREATE_DEST.
DB_CREATE_FILE_DEST
DB_RECOVERY_FILE_DEST

For redolog, if DB_RECOVERY_FILE_DEST is not set, or DB_CREATE_ONLINE_LOG_DEST_n, the directory specified by the DB_CREATE_FILE_DEST parameter is used for storage.

SQL> show parameter DB_CREATE_ONLINE_LOG_DEST
NAME TYPE VALUE
-----------------------------------------------------------------------------
Db_create_online_log_dest_1 string
Db_create_online_log_dest_2 string
Db_create_online_log_dest_3 string
Db_create_online_log_dest_4 string
Db_create_online_log_dest_5 string

If the db_create_online_log_dest _ * parameter is specified separately, redolog member will be redundant to these separately specified directories.

Supported options for naming online redo logs duplicated from Oracle-managed files are DB_CREATE_FILE_DEST,

DB_RECOVERY_FILE_DEST, or DB_CREATE_ONLINE_LOG_DEST_n.

---- The DB_CREATE_ONLINE_LOG_DEST_n parameter is interpreted as redolog. The control file specifies the storage directory. If multiple parameters are specified, multiplexing is enabled.
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. if more than one DB_CREATE_ONLINE_LOG_DEST_n parameter is specified, then the control file or online redo log is multiplexed processing ss the locations of the other DB_CREATE_ONLINE_LOG_DEST_n parameters. one member of each online redo log is created in each location, and one control file is created in each location.


Specifying at least two parameters provides greater fault tolerance for the control files and online redo logs if one of the locations showould fail.

If a file system directory is specified as the default location, then the directory must already exist; Oracle does not create it. the directory must have appropriate permissions that allow Oracle to create files in it. oracle generates unique names for the files, and a file thus created is an Oracle Managed File.

For file systems, the specified directory must have accurate permissions and already exists. If not, oracle will not automatically create

Copyright Disclaimer: This article is an original article by the blogger and cannot be reproduced without the permission of the blogger.