SET

Syntax

set::=

setRmanOption::=

setRunOption::=

Purpose

You can use the SET command either at the RMAN prompt or within a RUN block.

When used outside a RUN block, attributes changed by SET remain in effect until you exit the RMAN client.

Outside of a RUN block, the SET command supports the attributes shown in "setRmanOption". Use this form of the SET command to:

• Cause RMAN to echo any commands executed in the message log

• Specify the location to search for control file autobackups during RESTORE operations

• Specify the database identifier (DBID) of a database, when restoring a control file or server parameter file from autobackup

• Specify a command ID for an RMAN command, so that rows in V$SESSION corresponding to sessions related to that command have V$SESSION.CLIENT_INFO set to this ID

• Specify settings related to encryption and decryption of backup sets for the duration of an RMAN session

• Specify the location to use for auxiliary instance datafiles, when performing TSPITR or creating transportable tablespaces sets from backup

Within a RUN block, the SET command supports the attributes shown in "setRunOption". Changes made with SET within a RUN block persist until the end of the RUN block, or the next SET command that changes the value of the same attribute.

Use SET specified within a RUN block to:

• Specify new filenames for restored datafiles

• Specify the filenames for the auxiliary database during TSPITR or database duplication.

• Specify a limit for the number of permissible block corruptions.

• Override default archived redo log destinations.

• Set an end time, SCN, or log sequence number for recovery.

• Specify that backup sets should be duplexed, that is, multiple copies should be created of each backup piece in the backup set.

• Determine which server session corresponds to which channel.

• Turn RMAN's automatic location feature on or off.

• Override the default format for control file autobackups at the session level.

Restrictions and Usage Notes for SET Command Within RUN

The following restrictions apply to SET when issued within a RUN command:

• The SET BACKUP COPIES command affects all backups in the RUN block after issuing the command and is in effect until explicitly disabled or changed. The SET BACKUP COPIES command does not affect previous backups.

• SET BACKUP COPIES does not apply to the BACKUP AS COPY command.

• You must include the %F substitution variable in the autobackup format.

• You cannot use SET NEWNAME TO NEW when creating a duplicate or standby database or performing RMAN TSPITR.

Restrictions and Usage Notes for the SET DBID Command

You should only run the SET DBID command in the following specialized circumstances:

• You are not connected to a recovery catalog and want to restore the control file or server parameter file.

• You are connected to a recovery catalog and want to restore the control file, but the database name is not unique in the recovery catalog.

• The server parameter file is lost and you want to restore it.

  
  

  See Also: Table 2-27 for RESTORE CONTROLFILE usage notes.

  
  

Keywords and Parameters

setRmanOption

% rman TARGET sys/pwd@prod1 CATALOG rman/rman@rcat < in_file > out_file

setRunOption

Examples

Restoring the Control File When Databases Share the Same Name: Example The following example uses the DBID to restore the control file because multiple target databases share the same DB_NAME in the catalog. After you have restored the target control file, you can mount the database to restore the rest of the database:

rman TARGET / CATALOG rman/rman@catdb 
RMAN> STARTUP FORCE NOMOUNT;
RMAN> SET DBID = 862893450; # needed to distinguish target from others with same DB_NAME
RMAN> RESTORE CONTROLFILE; # assuming catalog has automatic channel allocation information
RMAN> ALTER DATABASE MOUNT;

Setting the Command ID: Example This example sets the command ID, backs up the users tablespace, then archives the online redo logs:

RUN
{
  ALLOCATE CHANNEL t1 DEVICE TYPE DISK FORMAT '/disk1/%U';
  ALLOCATE CHANNEL t2 DEVICE TYPE DISK FORMAT '/disk2/%U';
  SET COMMAND ID TO 'rman';
  BACKUP INCREMENTAL LEVEL 0 MAXSETSIZE 5M TABLESPACE users;
  SQL 'ALTER SYSTEM ARCHIVE LOG ALL';

}

Duplexing a Backup Set: Example Assume that you have used the CONFIGURE command to set duplexing as follows:

CONFIGURE ARCHIVELOG COPIES FOR DEVICE TYPE sbt TO 4;
CONFIGURE DATAFILE COPIES FOR DEVICE TYPE sbt TO 3;

The following example overrides these configurations and makes two copies of each datafile and archived log in the backup:

RUN
{
  ALLOCATE CHANNEL dev1 DEVICE TYPE sbt;
  SET BACKUP COPIES = 2;
  BACKUP DATAFILE 1,2,3,4,5;
  BACKUP ARCHIVELOG ALL;
}

Overriding the Autobackup Format During a Restore: Example This example sets the DBID, sets a boundary time for the restore, then restores a control file autobackup with a nondefault format. First start RMAN and then run:

CONNECT TARGET / NOCATALOG
STARTUP FORCE NOMOUNT
SET DBID 676549873;
RUN
{
  SET UNTIL TIME '10/10/2001 13:45:00';
  SET CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK TO '?/oradata/cf_%F.bak';
  RESTORE CONTROLFILE FROM AUTOBACKUP MAXSEQ 100;
}
ALTER DATABASE MOUNT;

Restoring the Server Parameter File: Example This example restores a lost server parameter file:

CONNECT TARGET / CATALOG rman/rman@catdb
SET DBID 676549873;  # set dbid so rman knows the database name
STARTUP FORCE NOMOUNT # rman starts database with a dummy server parameter file
RESTORE SPFILE;
STARTUP FORCE; # needed so that RMAN restarts database with restored server parameter file