26 Duplicating a Database: Advanced Topics

1. Follow Steps 1 through 4 in "Basic Steps of Database Duplication".
2. Within a RUN command, issue the SET NEWNAME command before issuing DUPLICATE.

   The following example illustrates a script that specifies new names for data files 1 through 5 and temp file 1. The script does not set a new name for data file 6 because it is in the TOOLS tablespace, which is excluded from the duplicate database.

   RUN
   {
     SET NEWNAME FOR DATAFILE 1 TO '/oradata1/system01.dbf'; 
     SET NEWNAME FOR DATAFILE 2 TO '/oradata2/sysaux01.dbf';
     SET NEWNAME FOR DATAFILE 3 TO '/oradata3/undotbs01.dbf';
     SET NEWNAME FOR DATAFILE 4 TO '/oradata4/users01.dbf'; 
     SET NEWNAME FOR DATAFILE 5 TO '/oradata5/users02.dbf';
     SET NEWNAME FOR TEMPFILE 1 TO '/oradatat/temp01.dbf'; 
     DUPLICATE TARGET DATABASE TO dupdb
       SKIP TABLESPACE tools
       LOGFILE
         GROUP 1 ('/duplogs/redo01a.log', 
                  '/duplogs/redo01b.log') SIZE 4M REUSE, 
         GROUP 2 ('/duplogs/redo02a.log', 
                  '/duplogs/redo02b.log') SIZE 4M REUSE;
   }
   

   The following example uses one SET NEWNAME command to name all data files in the tablespace users. After the example completes, the file names for tablespace users are set to: /oradata4/users01.dbf and /oradata5/users02.dbf.

   RUN
   {
     SET NEWNAME FOR TABLESPACE users TO '/oradata%f/%b';
     SET NEWNAME FOR DATAFILE 1 TO '/oradata1/system01.dbf'; 
     SET NEWNAME FOR DATAFILE 2 TO '/oradata2/sysaux01.dbf';
     SET NEWNAME FOR DATAFILE 3 TO '/oradata3/undotbs01.dbf'; 
     SET NEWNAME FOR TEMPFILE 1 TO '/oradatat/temp01.dbf'; 
     DUPLICATE TARGET DATABASE TO dupdb
       SKIP TABLESPACE tools
       LOGFILE
         GROUP 1 ('/duplogs/redo01a.log', 
                  '/duplogs/redo01b.log') SIZE 4M REUSE, 
         GROUP 2 ('/duplogs/redo02a.log', 
                  '/duplogs/redo02b.log') SIZE 4M REUSE;
   }
   

   The following command uses a single SET command to name all data files in the database.

   RUN
   {
     SET NEWNAME FOR DATABASE TO '/oradata/%U'; 
     DUPLICATE TARGET DATABASE TO dupdb
       SKIP TABLESPACE tools
       LOGFILE
         GROUP 1 ('/duplogs/redo01a.log', 
                  '/duplogs/redo01b.log') SIZE 4M REUSE, 
         GROUP 2 ('/duplogs/redo02a.log', 
                  '/duplogs/redo02b.log') SIZE 4M REUSE;
   }
   

1. Issue a CONFIGURE AUXNAME command for each file to name in the duplicate database.

   For example, enter the following commands at the RMAN prompt to specify names for files data files 1 through 5:

   CONFIGURE AUXNAME FOR DATAFILE 1 TO '/oradata1/system01.dbf'; 
   CONFIGURE AUXNAME FOR DATAFILE 2 TO '/oradata2/sysaux01.dbf';
   CONFIGURE AUXNAME FOR DATAFILE 3 TO '/oradata3/undotbs01.dbf';
   CONFIGURE AUXNAME FOR DATAFILE 4 TO '/oradata4/users01.dbf'; 
   CONFIGURE AUXNAME FOR DATAFILE 5 TO '/oradata5/users02.dbf';
   

2. Issue a DUPLICATE command.

   For example, enter the following command at the RMAN prompt:

   SET NEWNAME FOR TEMPFILE 1 TO '/oradatat/temp01.dbf'; 
   DUPLICATE TARGET DATABASE
     TO dupdb
     SKIP TABLESPACE tools
     LOGFILE
       GROUP 1 ('/duplogs/redo01a.log',
                '/duplogs/redo01b.log') SIZE 4M REUSE,
       GROUP 2 ('/duplogs/redo02a.log',
                '/duplogs/redo02b.log') SIZE 4M REUSE;
   

   RMAN uses the CONFIGURE AUXNAME settings to name data files 1 through 5.

When creating a duplicate database that uses Oracle Managed Files, you must set initialization parameters in the auxiliary instance. If you use the SPFILE clause of DUPLICATE to name the files, then you can set initialization parameters in the SPFILE clause. Table 26-3 describes the relevant parameters and recommended settings and Table 26-4 lists the restrictions on setting other initialization parameters

The procedure for creating a duplicate database to an ASM location is similar to the procedure described in "Settings and Restrictions for OMF Initialization Parameters ". The difference is that you must identify the initialization parameters that control the location where files are created and set these parameters to an ASM disk group. For example, set DB_CREATE_FILE_DEST, DB_CREATE_ONLINE_DEST_n, and CONTROL_FILES to +DISK1.

1. Set the DB_CREATE_FILE_DEST initialization parameter at the auxiliary instance to the desired location
2. Enclose the DUPLICATE command in a RUN block and use SET NEWNAME with the TO NEW option for Oracle Managed Files.

   The following example illustrates a script that specifies literal names for data files 1-5. The only Oracle Managed Files in the source database are the data files in the users tablespace. Therefore, TO NEW is specified in the SET NEWNAME command for these files.

   RUN
   {
     SET NEWNAME FOR TABLESPACE users TO NEW;
     SET NEWNAME FOR DATAFILE 3 TO NEW;
     SET NEWNAME FOR DATAFILE 1 TO '/oradata1/system01.dbf'; 
     SET NEWNAME FOR DATAFILE 2 TO '/oradata2/sysaux01.dbf';
     SET NEWNAME FOR TEMPFILE 1 TO '/oradatat/temp01';  
     DUPLICATE TARGET DATABASE TO dupdb
       SKIP TABLESPACE tools
       LOGFILE
         GROUP 1 ('/duplogs/redo01a.log', 
                  '/duplogs/redo01b.log') SIZE 4M REUSE, 
         GROUP 2 ('/duplogs/redo02a.log', 
                  '/duplogs/redo02b.log') SIZE 4M REUSE;
   }
   

   As shown in the following example, you can also use SET NEWNAME to direct individual data files, temp files, or tablespaces to a specified ASM disk group.

   RUN
   {
      SET NEWNAME FOR DATAFILE 1 TO "+DGROUP1";
      SET NEWNAME FOR DATAFILE 2 TO "+DGROUP2";
      .
      .
      .
      DUPLICATE TARGET DATABASE 
        TO dupdb
        FROM ACTIVE DATABASE
        SPFILE SET DB_CREATE_FILE_DEST +DGROUP3;
   }
   

If the LOG_FILE clause has been omitted and no Oracle Managed Files initialization parameters DB_CREATE_FILE_DEST, DB_CREATE_ONLINE_DEST_n, or DB_RECOVERY_FILE_DEST are specified, then LOG_FILE_NAME_CONVERT can transform target file names. This works in much the same way as the DB_FILE_NAME_CONVERT and can transform target file names from log_* to duplog_*. You can specify multiple conversion file name pairs with this parameter.

When you specify LOG_FILE_NAME_CONVERT, RMAN uses the REUSE parameter when creating the online redo logs. If an online redo log file exists at the named location and is of the correct size, then it is reused for the duplicate.