This subclause specifies the online redo logs when creating a duplicate database that is not a standby database. This section assumes the same circumstances described in Example 2-87. Auxiliary channels have been configured with the CONFIGURE CHANNEL command. You want to store the data files in desthost in the /oradata1 through /oradata7 subdirectories. For backup-based duplication of databases without a connection to the target database, RMAN cannot determine whether the source database was in NOARCHIVELOG mode. In this scenario, srchost and desthost have different directory structures. These tablespaces cannot be skipped and the set of tablespaces that you want to duplicate must be self-contained.

Duplicates all the PDBs within the CDB, except the ones specified in the comma-separated list pdb_name. To specify different file names for the temp files, see the discussion of SWITCH TEMPFILE . This clause enables you to duplicate a database or tablespace. You must use the RMAN client on the same host as the initialization parameter file for the duplicate database. Specifies a text-based initialization parameter file used by the auxiliary instance (see Example 2-85). If the source database is not open, then it must have been shut down consistently. Assume all backups needed to create the standby database are stored on tape. You are responsible for determining that the duplicate operation does not overwrite useful data. Because the limit is inclusive, RMAN selects only files that it can use to duplicate a database up to and including the corresponding SCN. Example 2-87 Using SET NEWNAME FOR DATAFILE and SET NEWNAME FOR TABLESPACE to Name Duplicate Files. Also, if a fast recovery area was defined on the source database, and if the auxiliary instance uses a server parameter file that was copied or restored with the DUPLICATE command, then a fast recovery area is defined on the duplicate or standby database. If you are duplicating the SPFILE, then specify a unique DB_UNIQUE_NAME in the SPFILE clause. Applies no archived redo log files when recovering a consistent backup in any of the following scenarios: You do not want to apply archived redo log files to the consistent backup even though the archived redo log files are available. The set of tablespaces to be duplicated must be self-contained. You decide to use the SET NEWNAME DATABASE command because you want all duplicate data files in the same directory on the destination host. Table 2-7 shows which files from the source database are duplicated. If you are using backup-based duplication, and if the source database and auxiliary instances reside on different hosts, then you must decide how to make the backups of the source database available to the auxiliary instance. For example, Linux IA (32-bit) is considered the same platform as Linux IA (64-bit). The source database is called prod1 and is the primary database in the Data Guard environment. The same number of online redo log files are used in the duplicate database. There are two ways to store specific data files or temp files in an Oracle-managed files destination that is independent of the locations of the rest of the database files. If you are using disk backups, and if you cannot use the same backup directory names on the destination host as the source host, then use of the techniques described in Oracle Database Backup and Recovery User's Guide. Prerequisites Specific to Active Database Duplication. Specifies the name of the duplicate database. You cannot use TO database_name for a standby database. Example 2-94 Duplicating PDBs and Specific Tablespaces in a PDB. To duplicate PDBs, you must connect to the root as described in "Connecting to CDBs and PDBs". A description of the environment follows: The source and destination hosts have identical directory structures. Refer to the dupOptionList::= diagram for the syntax. Active database duplication with image copies uses the auxiliary net service name to copy the source database over the network to the auxiliary instance on the destination host. The source database name prod is unique in the recovery catalog. The DUPLICATE command must have been issued with the DATABASE clause. DB_FILE_NAME_CONVERT set on the DUPLICATE command overrides the initialization parameter DB_FILE_NAME_CONVERT (if set). Allocate multiple channels to the target instance and a channel to the auxiliary instance as shown here: You can then enter the following command: Example 2-84 Duplicating a Database Without a Target Connection to a Host with the Same Directory Structure. RMAN leaves the standby database mounted after media recovery is complete, but does not place the standby database in manual or managed recovery mode. RMAN can create either of the following types of databases: A duplicate database, which is a copy of the source database (or a subset of the source database) with a unique DBID. Sets the end time, SCN, or log sequence number for point-in-time recovery in backup-based duplication (see Example 2-85). Typically, the source and duplicate databases must be on the same platform; however some cross-platform duplication is supported. Set the parameter DB_CREATE_FILE_DEST in the initialization parameter file of the auxiliary instance to the desired location. Otherwise, you do not need to use INSTANCE. Table 2-6 Prerequisites for Three Modes of Backup-Based Duplication. Otherwise, RMAN cannot duplicate transportable tablespaces unless they have been made read/write after being transported. If the database was in an archiving mode at the specified UNTIL time or SCN that is different from the current archiving mode, then RMAN does not use NOREDO. The DUPLICATE FOR STANDBY command creates the standby database by restoring a standby control file and mounting the standby control file. Setting DB_DOMAIN enables you to connect with RMAN to the default database service. Uses the password file on the source database to overwrite the password file currently used by the auxiliary instance (see Example 2-82). RMAN creates duplicate files from pre-existing RMAN backups and copies. Replaces the first string with the second string in all matching initialization parameter values. It is invalid to specify INCARNATION when connected to a target database or when using BACKUP LOCATION. This form requires a connection to an auxiliary instance and a recovery catalog. As shown in the following sample script, you can also use SET NEWNAME to direct individual data files or temp files to a specific ASM disk group. You cannot CONNECT RMAN to the standby database and then use DUPLICATE FOR STANDBY to create an additional standby database.

Excludes data files in current read-only tablespaces from the duplicate database. You can then enter the following RUN command: Example 2-86 Using SET NEWNAME FOR DATABASE to Name Duplicate Files. For example, if the initialization parameter file setting is DB_FILE_NAME_CONVERT=('disk1','disk2'), but you execute DUPLICATE DB_FILE_NAME_CONVERT ('disk1','disk3'), then RMAN does not convert the disk1 substring to disk2. You can make this backup accessible in the following ways: Use NFS to mount the backup on the destination host with the same name. If PARAMETER_VALUE_CONVERT sets the file name specified by a parameter, and if SET sets the file name specified by the same parameter, then the SET value overrides the PARAMETER_VALUE_CONVERT setting. You create a text-based initialization parameter file on desthost and use it to start the database instance. You cannot recover the duplicate database to the current point in time, that is, the most recent SCN. Otherwise, RMAN can potentially overwrite and corrupt the target database data files, temp files, or online logs. 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. Start the RMAN client on desthost, CONNECT to the source database as TARGET, and connect to the auxiliary instance.

In this example, /backups contains backups from several databases, including more than two databases with the name PROD. If a tablespace is currently read/write, but you use untilClause to duplicate the database to an SCN at which the tablespace was read-only, then RMAN does not include the tablespace in the duplicate database. The data files are not Oracle Managed Files. First, start the RMAN client, CONNECT to the source database prod1 as TARGET, and connect to the auxiliary instance. These new file names are recorded in the control file and used every time you perform the duplication in the future. RMAN uses all incremental backups, archived redo log backups, and archived redo log files to perform incomplete recovery and then opens the database with the RESETLOGS option to create the online redo logs. In the standby database initialization parameter file, you set DB_UNIQUE_NAME to standby1. You want to store the data files in desthost in the /oradata1 subdirectory, so you use SET NEWNAME FOR DATABASE to specify the file names stripped of directory paths. Example 2-92 Duplicating a Database Without Connection to Target Database and Recovery Catalog. Specifies the database ID (DBID) of the source database. In this example, the PDBs pdb1, pdb5, and the users tablespace in PDB pdb2 are duplicated. Copies the server parameter file from the source database to the duplicate database. The name of the tablespace in a CDB. You use DUPLICATE LOGFILE to specify names for the online redo log files in the duplicate database. You want to store the duplicate database files in ASM disk group +DUPDSK. 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 the duplicate database. This location is where only backups of database prod reside. The source database does not use a server parameter file, so you cannot use the SPFILE technique to specify names for the duplicate data files. If you want the duplicate database to contain all the passwords available on your source database, then use the PASSWORD FILE option. A standby database is not assigned a new DBID. Yes (if no catalog used and target is not open). This mode is useful when the target database is not available or a connection to it is not desirable (as mandated by security policy restrictions or a firewall). In this case, you must specify the DBNAME and the DBID of the database to duplicate. The source database is currently running in ARCHIVELOG mode but the backup was taken when the database was in NOARCHIVELOG mode. Enter the following command to create the standby database: RMAN automatically generates new OMF/ASM data file names for the restored data files. All backups and archived redo log files used for creating and recovering the duplicate database must be accessible by the server session on the destination host. Note: The read-only tablespaces must be self-contained for the DUPLICATE command to succeed with this option. For more information on how to do this with BACKUP LOCATION, review the options described in the section Making Disk Backups Accessible to the Auxiliary Instance in the Oracle Database Backup and Recovery User's Guide. If not, then manually set this parameter to a unique value in the PFILE or SPFILE of the auxiliary instance. As shown in Table 2-6, the prerequisites for backup-based duplication depend on whether RMAN is connected as TARGET to the source database. For example, set DB_CREATE_FILE_DEST to +DATAFILE and DB_RECOVERY_FILE_DEST to +FLASH_REC_AREA. Enables binary compression of the data transfer from the source database to the auxiliary database, thereby reducing the network bandwidth consumption. All tablespaces taken offline with an option other than NORMAL. You cannot use SET NEWNAME or CONFIGURE AUXNAME to transform the file names for the online redo logs on the standby database. The DUPLICATE command enables you to duplicate CDBs, the root, and one or more PDBs. In this example, all the necessary backups of data files, controlfile and archived logs of database prod can be accessed from the location: /net/prod/backups. For example, assume that you create the standby control file and then immediately afterward archive the current log, which has a sequence of 100. Unlike SKIP TABLESPACE, which specifies which tablespaces are excluded from the duplicate database, this option specifies which tablespaces are included and then skips the remaining tablespaces. If the auxiliary instance uses a server parameter file in the default location, then you do not need to specify PFILE. These channels perform the work of the duplication on the auxiliary database instance. UNTIL clause must be specified in the current incarnation. Start the RMAN client, CONNECT to database prod1 as TARGET, connect to the standby1 instance as AUXILIARY, and connect to the recovery catalog. You set the following parameters in the initialization parameter file for database standby1: Set DB_UNIQUE_NAME to the value standby1. This check is performed automatically by RMAN when backup based duplication with a target connection is performed. The only connection is to the auxiliary instance. Start the RMAN client, connect to the source and auxiliary database instances with net service names, and duplicate the database as follows: Example 2-83 Copying the Server Parameter File in Active Database Duplication. When you connect RMAN to the standby database and the recovery catalog in which the primary database is registered, RMAN recognizes the standby database and implicitly registers it. If you configure or manually allocate channels for active duplication with backup sets, ensure that the number of auxiliary channels is greater then or equal to the number of target channels. All data files are included in the duplicate database unless they are offline clean or excluded. Specifies the name of the source database, which is the database to duplicate. The source database was running in NOARCHIVELOG mode at backup time and DUPLICATE is not connected to the target database. The auxiliary instance uses a server-side initialization parameter file in the default location so the PFILE parameter is not necessary on the DUPLICATE command. These backups and copies exist in the same location on desthost as they do in srchost. Also, you want the duplicate database to be in the state that the production database was in 24 hours ago, so you use DUPLICATE UNTIL TIME. The default is in bytes. If you specify the UNTIL clause for duplication, then the following restrictions apply: RMAN determines whether to use NOREDO based on the current state of the database. When this option is used, RMAN uses active duplication with backup sets by default. Backup sets offer several advantages, including unused block compression and encryption. Performs active database duplication by copying all or a subset of data from the source database to the destination database using backup sets. The source database and auxiliary instances must use the same SYS and SYSBACKUP password, which means that both instances must have password files. You can use SET to adjust for differences in memory, turn off replication options, and set other options for the duplicate database. If you create a duplicate database that is not a standby database, then RMAN does not copy the password file by default. If the source database is open, then archiving must be enabled. For example, enter the following commands: Alternatively, you may want to periodically synchronize a duplicate database with the original database that was duplicated. The destination host is the host on which you intend to create the duplicate database. Because a duplicate database has a unique DBID, it is independent of the source database and can be registered in the same recovery catalog. You can specify the PASSWORD FILE option to indicate that RMAN can overwrite the existing password file on the auxiliary instance. This technique requires making complete copies of the data files of the duplicate database. 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. Also, set all *_DEST or other related initialization parameters appropriately so that the source database files are not overwritten by the duplicate database files. In this case, the PASSWORD FILE clause is not necessary. The source database does not use a server parameter file, so you cannot use the SPFILE technique to specify names for the duplicate data files. The following DUPLICATE command uses the DBID parameter to uniquely identify the source database: Example 2-85 Setting New File Names in the DUPLICATE Command. Set DB_FILE_CREATE_DEST to make all data files of the new database Oracle-managed files, except the files for which SET NEWNAME is used. After the duplication is complete, you can clear the configured auxiliary names for the data files in the duplicate database, so that they are not overwritten by future operations. In this case the RUN command is not necessary because you are not using SET NEWNAME. A recovery catalog is available. Active duplication can use image copies or backup sets. Note: You cannot use SKIP TABLESPACE while creating a standby database. Specifies the PDB when connected to a PDB.

Specifies the size of each backup section produced during the data transfer phase of the active duplicate operation. You have reset all initialization parameters that end in _DEST and specify a path name. See dupOptionList. If you intend to create the duplicate database on the source host, then set the CONTROL_FILES initialization parameter appropriately so that the DUPLICATE command does not generate an error because the source control file is in use.