Using RMAN DUPLICATE DATABASE: Examples

Duplicating When the Datafiles Use Inconsistent Paths: Example

This example assumes the following:

• You are using recovery catalog database catdb.

• The target database trgt is on host1 and contains eight datafiles, which are spread out over multiple directories.

• You want to exclude tablespace tools from the duplicate database, but keep all of the other tablespaces.

• You want to duplicate the target to database dupdb on remote host host2.

• host1 and host2 cannot mount each other's file systems by any means such as NFS.

• You want to store the datafiles in host2 in the /oradata1, /oradata2 ... through /oradata7 subdirectories.

• You have used an operating system utility to copy the initialization parameter file from host1 to an appropriate location in host2.

• You have reset all initialization parameters that end in _DEST and specify a path name.

• You want two online redo logs groups, each with two members of size 200 KB, which on the duplicate system will be stored in the directory "/duplogs".

• You have disk copies or backup sets stored on disk for all the datafiles and archived redo logs in the target database, and you have manually moved them to host2 by means of an operating system utility.

• 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).

Example 13-3 illustrates a script that creates the duplicate database.

CONNECT TARGET /;
CONNECT CATALOG rman/cat@catdb;
CONNECT AUXILIARY SYS/oracle@dupdb;

# note that a RUN command is necessary because you can only execute SET NEWNAME
# within a RUN command
RUN
{
  # The DUPLICATE command uses an automatic sbt channel.
  # Because the target datafiles are spread across multiple directories, 
  # run SET NEWNAME rather than DB_FILE_NAME_CONVERT
  SET NEWNAME FOR DATAFILE 1 TO '/oradata1/system01.dbf'; 
  SET NEWNAME FOR DATAFILE 2 TO '/oradata2/undotbs01.dbf'; 
  SET NEWNAME FOR DATAFILE 3 TO '/oradata3/cwmlite01.dbf'; 
  SET NEWNAME FOR DATAFILE 4 TO '/oradata4/drsys01'; 
  SET NEWNAME FOR DATAFILE 5 TO '/oradata5/example01.dbf'; 
  SET NEWNAME FOR DATAFILE 6 TO '/oradata6/indx01.dbf';
  # Do not set a newname for datafile 7, because it is in the tools tablespace,
  # and you are excluding tools from the duplicate database.
  SET NEWNAME FOR DATAFILE 8 TO '/oradata7/users01.dbf'; 
  DUPLICATE TARGET DATABASE TO dupdb
    SKIP TABLESPACE tools
    LOGFILE
      GROUP 1 ('/duplogs/redo01a.log', 
               '/duplogs/redo01b.log') SIZE 200K REUSE, 
      GROUP 2 ('/duplogs/redo02a.log', 
               '/duplogs/redo02b.log') SIZE 200K REUSE;
}

RMAN DUPLICATE DATABASE From File System to ASM: Example

This duplication example assumes the following:

• You are using recovery catalog database catdb.

• The target database trgt is on host1 and the database files are stored in a non-ASM file system.

• You want to duplicate the target to database dupdb on remote host host2.

• host2 has diskgroup +DISK1.

• You want to store the datafiles for dupdb to +DISK1.

• You want to store two controlfiles in +DISK1.

• The backups and archivelogs created by host1 are accessible by host2.

Create an initialization parameter for auxiliary instance by copying the target database initialization parameter file. Change the parameters as follows:

• Set DB_NAME to the new database name dupdb

• Set CONTROL_FILES to store two copies of the control file in +DISK1

• Make sure DB_FILE_NAME_CONVERT and LOG_FILE_NAME_CONVERT are not set

• Set any other initialization parameters that end in _DEST, such as DB_CREATE_FILE_DEST and DB_CREATE_ONLINE_DEST_n, to reference +DISK1

For example:

DB_NAME=dupdb
CONTROL_FILES=+DISK1,+DISK1

Create an SPFILE from the parameter file, and start the auxiliary instance:

SQL> CONNECT AUXILIARY SYS/oracle@dupdb;
SQL> CREATE SPFILE FROM PFILE=auxiliary instance pfile;
SQL> STARTUP NOMOUNT;

Then run the following RMAN commands to duplicate the database:

RMAN> CONNECT TARGET /;
RMAN> CONNECT CATALOG rman/cat@catdb;
RMAN> CONNECT AUXILIARY SYS/oracle@dupdb;
RMAN> DUPLICATE TARGET DATABASE TO dupdb
      LOGFILE GROUP 1 ('+DISK1','+DISK1') SIZE 200K,
              GROUP 2 ('+DISK1','+DISK1') SIZE 200K;

When the DUPLICATE command completes, the duplicate database is created, with datafiles, online logs and control files in ASM disk group +DISK1.

RMAN DUPLICATE DATABASE From ASM to ASM: Example

This duplication example assumes the following:

• You are using recovery catalog database catdb

• The target database trgt is on host1 and contains ASM datafiles and online logs in diskgroup +DISK1

• You want to duplicate the target to database dupdb on remote host host2.

• host2 has diskgroup +DISK2

• You want to store the datafiles for dupdb to +DISK2

• You want to store two controlfiles in +DISK2

• The backups and archivelogs created by host1 are accessible by host2

Create an initialization parameter for auxiliary instance by copying the target database initialization parameter file. Change the parameters as follows:

• Set DB_NAME to the new database name dupdb

• Set CONTROL_FILES to store two copies of the control file in +DISK2

• Set DB_FILE_NAME_CONVERT and LOG_FILE_NAME_CONVERT to convert the datafile and online log file names from +DISK1 to +DISK2

• Set any other initialization parameters that end in _DEST, such as DB_CREATE_FILE_DEST and DB_CREATE_ONLINE_DEST_n, to reference +DISK2

For example:

DB_NAME=dupdb
CONTROL_FILES=+DISK2,+DISK2
DB_FILE_NAME_CONVERT=+DISK1,+DISK2
LOG_FILE_NAME_CONVERT=+DISK1,DISK2

Create an SPFILE from the parameter file, and start the auxiliary instance:

SQL> CONNECT AUXILIARY SYS/oracle@dupdb;
SQL> CREATE SPFILE FROM PFILE=auxiliary instance pfile;
SQL> STARTUP NOMOUNT;

Then run the following RMAN commands to duplicate the database:

RMAN> CONNECT TARGET /;
RMAN> CONNECT CATALOG rman/cat@catdb;
RMAN> CONNECT AUXILIARY SYS/oracle@dupdb;
RMAN> DUPLICATE TARGET DATABASE TO dupdb;

When the DUPLICATE command completes, the duplicate database is created, with datafiles, online logs and control files in ASM disk group +DISK2.

RMAN DUPLICATE DATABASE at a Past Point in Time: Example

This duplication example assumes the following:

• The target database trgt and duplicate database dupdb are on different hosts but have exactly the same directory structure.

• You want to name the duplicate database files the same as the target files.

• You are not using a recovery catalog.

• You are using automatic channels for disk and sbt, which are already configured.

• You want to recover the duplicate database to one week ago in order to view the data in prod1 as it appeared at that time (and you have the required backups and logs to recover the duplicate to that poin tin time).

CONNECT TARGET SYS/oracle@trgt
CONNECT AUXILIARY SYS/oracle@dupdb

DUPLICATE TARGET DATABASE TO dupdb 
    NOFILENAMECHECK UNTIL TIME 'SYSDATE-7';

Duplicating with a Client-Side Parameter File: Example

You can run the DUPLICATE command using a client-side parameter file for the auxiliary instance. Assume the following scenario:

• The target host is host_src and the duplicate host is host_dup.

• The client-side initialization parameter file on host_dup is named /tmp/initTEST.ora.

• The hosts host_dup and host_src are linked by a network.

In this scenario, you can run the RMAN client (that is, run the DUPLICATE command in an RMAN session) either on host_src or host_dup.

DUPLICATE  
  TARGET DATABASE TO dupdb
  DEVICE TYPE sbt
  PFILE='/tmp/initTEST.ora';

% rman TARGET SYS/oracle@trgt AUXILIARY SYS/oracle@dupdb
RMAN> DUPLICATE TARGET DATABASE TO dupdb
        DEVICE TYPE sbt PFILE='/net/host_src/tmp/initTEST.ora';
RMAN> EXIT