####CHAPTER 4 #######: Rman Target Sys/oracle@mydb Catalog Rman1/rman1@rmandb
####CHAPTER 4 #######: Rman Target Sys/oracle@mydb Catalog Rman1/rman1@rmandb
####CHAPTER 4 #######
RMAN> SHOW ALL; # shows all CONFIGURE settings, both user-entered and default
2
example
RMAN> CONFIGURE CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE DISK CLEAR;
After configuring an sbt (that is, tape or media management) device according to the instructions in your media
management vendor documentation, you can make the media manager the default device:
To configure disk as the default device for backups, you can either use CONFIGURE... CLEAR to restore the default setting, or explicitly
configure the default device as shown:
RMAN> CONFIGURE DEFAULT DEVICE TYPE TO DISK;
Note:
You can always direct backups to a specific device type, DISK or SBT, using the DEVICE TYPEclause of the BACKUP command. For
example:
The default for backups to disk, as with tape, is backup set. Note that there is no analogous option for media manager devices,
because RMAN can only write backups to media manager devices as backup sets.
You can configure RMAN to use compressed backupsets by default on a particular device type, by using the CONFIGURE DEVICE
TYPE command with the BACKUP TYPE TO COMPRESSED BACKUPSET option, as shown in the following examples.
To disable compression, use the CONFIGURE DEVICE TYPE command with arguments specifying your other desired settings, but
omitting the COMPRESSED keyword, as in the following examples:
The following command configures RMAN to write disk backups to the /backup directory (refer to "Backing Up Database
Files and Archived Logs with RMAN").:
The format specifier %t is replaced with a four byte time stamp, %s with the backup set number, and %pwith the backup
piece number.
You can also configure an Automatic Storage Management disk group as your destination, as in the following example:
####### Configuring Control File and Server Parameter File AutoBackup #########
RMAN can be configured to automatically back up the control file and server parameter file whenever the database
structure metadata in the control file changes and whenever a backup record is added.The autobackup enables RMAN to
recover the database even if the current control file, catalog, and server parameter file are lost.
Because the filename for the autobackup uses a well-known format, RMAN can search for it without access to a
repository, and then restore the server parameter file. After you have started the instance with the restored server
parameter file, RMAN can restore the control file from an autobackup. After you mount the control file, the RMAN
repository is available and RMAN can restore the datafiles and find the archived redo log.