24 Duplicating a Database: Advanced Topics

Using SET NEWNAME to Name File System Datafiles and Tempfiles

As shown in Table 24-1, one way to name duplicate datafiles is to use the SET NEWNAME command before executing the DUPLICATE command. RMAN supports the following commands, listed in order of precedence:

1. SET NEWNAME FOR DATAFILE and SET NEWNAME FOR TEMPFILE

2. SET NEWNAME FOR TABLESPACE

3. SET NEWNAME FOR DATABASE

The order of precedence means that SET NEWNAME FOR TABLESPACE specifies names for files not already named by SET NEWNAME FOR DATAFILE and SET NEWNAME FOR TEMPFILE, while SET NEWNAME FOR DATABASE specifies names for files not already named by SET NEWNAME FOR TABLESPACE, SET NEWNAME FOR DATAFILE or SET NEWNAME FOR TEMPFILE.

When using SET NEWNAME FOR DATAFILE, you can specify a full path as a literal, as in /oradata1/system01.dbf. When using SET with FOR DATABASE or FOR TABLESPACE, however, you must use at least one of the first three substitution variables summarized in Table 24-1 (%I and %N are optional).

To use SET NEWNAME to specify new filenames:

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.

   Example 24-1 illustrates a script that specifies new names for datafiles 1 through 5 and tempfile 1. The script does not set a new name for datafile 6 because it is in the tools tablespace, which is excluded from the duplicate database.

   Example 24-1 Duplicating with SET NEWNAME FOR DATAFILE

   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;
   }
   

   Example 24-2 is a variation of Example 24-1 and uses one SET NEWNAME command to name all datafiles in the tablespace users. Once the example completes, the filenames for tablespace users are set to: /oradata4/users01.dbf and /oradata5/users02.dbf.

   Example 24-2 Duplicating with SET NEWNAME FOR DATAFILE and FOR TABLESPACE

   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;
   }
   

   Example 24-3 is a variation of Example 24-1 and uses a single SET command to name all datafiles in the database.

   Example 24-3 Duplicating with SET NEWNAME FOR 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;
   }
   

Assume the following:

• DBID is 87650928

• Database name is PROD

Using CONFIGURE AUXNAME to Name File System Datafiles and OMF/ASM Target Datafiles

CONFIGURE AUXNAME is an alternative to SET NEWNAME. The difference is that after you configure the auxiliary name the first time, additional DUPLICATE command reuse the configured settings. In contrast, you must reissue the SET NEWNAME command every time you execute the DUPLICATE command.

To use CONFIGURE AUXNAME to specify names for duplicate datafiles:

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

   For example, enter the following commands at the RMAN prompt to specify names for files datafiles 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 datafiles 1 through 5.

Setting and Restrictions for OMF Initialization Parameters

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 24-3 describes the relevant parameters and recommended settings and Table 24-4 lists the restrictions and initialization parameters that should not be set.

Setting Initialization Parameters for ASM

The procedure for creating a duplicate database to an ASM location is similar to the procedure described in "Setting 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.

DUPLICATE TARGET DATABASE TO dupdb
  FROM ACTIVE DATABASE
  SPFILE 
    PARAMETER_VALUE_CONVERT '/oracle/oradata/prod/', '+DISK1'
    SET DB_CREATE_FILE_DEST +DISK1;

DUPLICATE TARGET DATABASE
  TO dupdb
  FROM ACTIVE DATABASE
  SPFILE PARAMETER_VALUE_CONVERT '+DISK1','+DISK2'
     SET DB_RECOVERY_FILE_DEST_SIZE='750G';

Using SET NEWNAME to Create OMF or ASM Files

To name Oracle Managed Files, you can use the same SET NEWNAME commands described in "Using SET NEWNAME to Name File System Datafiles and Tempfiles", but with TO NEW instead of TO "filename". RMAN creates the specified datafiles or tempfiles with Oracle Managed File names in the location specified by DB_CREATE_FILE_DEST.

To use SET NEWNAME to specify names for Oracle Managed Files:

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.

   Example 24-6 illustrates a script that specifies literal names for datafiles 1-5. The only Oracle Managed Files in the source database are the datafiles in the users tablespace, therefore TO NEW is specified in the SET NEWNAME command for these files.

   Example 24-6 Duplicating with SET NEWNAME FOR DATAFILE and FOR TABLESPACE

   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 Example 24-7, you can also use SET NEWNAME to direct individual datafiles, tempfiles, or tablespaces to a specified ASM disk group.

   Example 24-7 Using SET NEWNAME to Create Files in an 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;
   }
   

Using the DB_FILE_NAME_CONVERT to Generate Names for Non-OMF or ASM Datafiles

Another technique to generate names besides using SET NEWNAME or CONFIGURE AUXNAME is to use DB_FILE_NAME_CONVERT to transform target filenames. For example, you can change the target filename from /oracle/ to /dup/oracle/. DB_FILE_NAME_CONVERT allows you to specify multiple conversion filename pairs. It can also be used to produce names for datafiles and tempfiles.

You can specify DB_FILE_NAME_CONVERT in the DUPLICATE command or you can set it in the initialization parameter of the auxiliary instance.

Using LOG_FILE_NAME_CONVERT to Generate Names for Non-OMF or ASM Logfiles

If the LOG_FILE clause has been omitted and none of the 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 transforms target filenames. This works in much the same way as the DB_FILE_NAME_CONVERT and can transform target filenames from log_* to duplog_*. You can specify multiple conversion filename 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 already exists at the named location and is of the correct size, then it is reused for the duplicate.