What's New in Recovery Manager?

This section describes new features of Recovery Manager in Oracle9i Release 2 (9.2) and provides pointers to additional information. New features information from previous releases is also retained to help those users migrating to the current release from releases prior to Oracle8i.

The following sections describe the new features in Recovery Manager:

• Oracle9i New Features in Recovery Manager
• Oracle8i New Features in Recovery Manager

Oracle9i New Features in Recovery Manager

This section contains these topics:

• Oracle9i Release 2 (9.2) New Features in Recovery Manager
• Oracle9i Release 1 (9.0.1) New Features in Recovery Manager

Oracle9i Release 2 (9.2) New Features in Recovery Manager

The Oracle9i Release 2 (9.2) features and enhancements increase manageability and expand functionality.

• Backup of Server Parameter Files

  The BACKUP command can back up the current server parameter file. RMAN automatically backs up the current server parameter file whenever it includes the current control file in a backup set. If the server parameter file is lost, then you can start an instance without a parameter file, and then run RESTORE SPFILE to restore it.

  See Also: Oracle9i Recovery Manager Reference for BACKUP syntax, and "Configuring the Control File and Server Parameter File Autobackup" to learn how to enable the control file autobackup feature

  
  
• Control File Autobackups After Structural Changes to the Database

  If CONFIGURE CONTROLFILE AUTOBACKUP is set to ON (it is OFF by default), then RMAN automatically backs up the control file and server parameter file after structural changes to the database. The target database records in the autobackup in the alert log.

  See Also: "Configuring the Control File and Server Parameter File Autobackup" to learn how to enable the control file autobackup feature

  
  
• Backing Up Archived Logs That Need Backups

  You can use NOT BACKED UP integer TIMES clause of the BACKUP ARCHIVELOG command to back up only those logs that have not been backed up at least integer times. When calculating the number of backups for a file, RMAN only considers backups created on the same device type as the current backup. This option is a convenient way to back up archived logs on specified media (for example, you want to keep at least three copies of each log on tape).

  See Also: Oracle9i Recovery Manager Reference for BACKUP syntax, and "Creating a Weekly Secondary Backup of Archived Logs: Example" for an example

  
  
• Managing Space When Restoring Archived Logs

  The MAXSIZE option of the RECOVER ... DELETE ARCHIVELOG command limits how much disk space RMAN uses when restoring logs during media recovery.

  See Also: Oracle9i Recovery Manager Reference for RECOVER syntax, and "Restoring and Recovering the Whole Database in the Default Location" for an example

  
  
• Automatic Tags for Backup and Copies

  If you do not specify a tag for a backup or copy, then RMAN automatically assigns one. The default format includes the date and time for the start of the backup.

  See Also: Oracle9i Recovery Manager Reference for a description of the default format for the TAG parameter of the BACKUP command

  
  
• DBNEWID Utility Changes DBID or Database Name

  You can use the DBNEWID utility to change the database name or DBID of a database. If you copy a database without using the RMAN DUPLICATE command, then the original and copied database share the same DBID. Because RMAN distinguishes databases by DBID, you cannot register multiple databases with the same DBID in the same recovery catalog. By using DBNEWID to change the DBID values for copied databases, you can register them in the same recovery catalog.

  See Also: Oracle9i Database Utilities to learn about the DBNEWID utility

  
  
• New V$ Views

  The V$DATABASE_BLOCK_CORRUPTION view records the corrupt blocks in a file after the most recent backup, backup validation, or copy of the file. The CORRUPTION_TYPE column shows the type of corruption. Run the BLOCKRECOVER command with the CORRUPTION LIST clause to recover all corrupt blocks recorded in the view. After a corrupt block is repaired, the row describing the corruption remains in the view until the next RMAN backup of the affected file. The V$DATABASE_BLOCK_CORRUPTION view has a corresponding recovery catalog view called RC_DATABASE_BLOCK_CORRUPTION.

  The V$DATABASE_INCARNATION view lists all incarnations of the database. A new incarnation is created whenever the database is opened with the RESETLOGS option. The V$DATABASE_INCARNATION view has a corresponding recovery catalog view called RC_DATABASE_INCARNATION.

  See Also: "Block Media Recovery with RMAN" for concepts, and Oracle9i Recovery Manager Reference for BLOCKRECOVER syntax

  
  
• Default Autolocation for Real Application Clusters

  RMAN automatically discovers which nodes of an Oracle Real Application Clusters configuration can access the files that you want to back up or restore. RMAN autolocates the following files:

  • Backup pieces during backup or restore
  • Archived redo logs during backup
  • Datafile or control file copies during backup or restore

  RMAN enables the autolocation feature whenever the allocated channels have different PARMS or CONNECT strings.

  Prior to Oracle9i Release 2, you had to manually enable this option with SET AUTOLOCATE, and the option only applied to backup pieces.

  See Also: "Automatic Location of Backups When Restoring in Real Application Clusters"

  
  
• Diagnostics for Media Manager Function Calls

  You can now query dynamic performance event views to obtain diagnostic data about RMAN calls to the media manager. An event name corresponds to every media management function. These event names can be used to diagnose problems during RMAN backup, restore, and maintenance jobs.

  See Also: "Monitoring RMAN Interaction with the Media Manager"

  
  
• FORCE Option for DELETE Command

  Sometimes the status of an object in the RMAN repository does not reflect the status of the object on the media. For example, someone deletes a backup piece with an operating system utility before CROSSCHECK is run. If the object is listed as AVAILABLE or EXPIRED but the reality on the media is otherwise, and if you run the DELETE command on the object, then RMAN does not delete it. You can override this behavior with the FORCE option of the DELETE command.

  See Also: "Behavior of DELETE Command When the Repository and Media Do Not Correspond"

  
  
• Deletion of Files Already Backed Up to a Device

  You can delete files that have already been backed up a specified number of times to a device. For example, you can delete all archived redo logs that have been backed up at least twice to tape.

  See Also: "Deletion of Archived Redo Logs That Are Already Backed Up"

  
  
• DUPLICATE Enhancements

  The SKIP TABLESPACE option of the DUPLICATE command enables you to exclude a list of tablespaces from the duplicate database. Also, you can specify the UNTIL clause on the DUPLICATE command to recover the duplicate database to a noncurrent time.

  See Also: "Database Duplication Options"

  
  
• RMAN Error Output Improved

  The RMAN error output is more compact and informative. If an RMAN command fails, then the error stack is always followed by RMAN-03002 or RMAN-03009 stating which command failed. If the errors are generated from the target database, then RMAN does not explicitly indicate that they are from the target database; however, if the errors are from the catalog or auxiliary database, then RMAN indicates this fact in a separate message.

Oracle9i Release 1 (9.0.1) New Features in Recovery Manager

The Oracle9i Release 1 (9.0.1) features and enhancements increase manageability and greatly expand functionality.

• Persistent RMAN Configurations

  The CONFIGURE command creates persistent RMAN settings that apply to any session. You can configure a variety of features including automatic channels, channel parallelism, retention policies, backup options, auxiliary filenames, and so forth.

  See Also: Chapter 8, "Configuring the Recovery Manager Environment" for configuration procedures, and Oracle9i Recovery Manager Reference for CONFIGURE syntax

  
  
• Automatic Channel Configuration

  The CONFIGURE command stores a persistent set of channel settings. RMAN automatically allocates these channels when you execute commands such as BACKUP or COPY at the RMAN prompt, abolishing the necessity for manual channel allocation.

  Use the CONFIGURE command to define backup attributes such as parallelism, duplexing, and channel control options. These settings are used by all commands that require channels unless you manually allocate channels in a RUN command.

  See Also: "Automatic and Manual Channel Allocation" for concepts, and Oracle9i Recovery Manager Reference for CONFIGURE syntax.

  
  
• More Commands Available at the RMAN Prompt

  Formerly, most backup and recovery commands had to be executed within a RUN command. Now, many commands such as BACKUP, COPY, and RESTORE can be executed at the RMAN prompt.

• Retention Policies

  A retention policy is a configuration that specifies how long backups of control files and datafiles should be retained, as well how many of these backups should be retained. The retention policy also determines which archived logs are obsolete because they are not needed to recover these backups.

  The REPORT OBSOLETE and DELETE OBSOLETE commands use the criteria specified in the retention policy to determine what is obsolete. You can specify a retention policy in these ways:

  • Using a recovery window, which defines a window of time extending backward from the present. The database must be recoverable to any point of time in that window.
  • Using redundancy, which specifies that any number of backups or copies beyond a specified number need not be retained.

    See Also: "Backup Retention Policies" for concepts, and Oracle9i Recovery Manager Reference for CONFIGURE syntax.

  
  
• Long-Term Backups Exempt from Retention Policy

  The KEEP option of the BACKUP command marks a backup as exempt from the retention policy. The REPORT OBSOLETE and DELETE OBSOLETE commands only consider the backup as obsolete when the KEEP time expires. You can alter the status of the backup with the CHANGE ... KEEP command.

  See Also: "Backups Exempt from the Retention Policy" for concepts, and Oracle9i Recovery Manager Reference for BACKUP syntax and Oracle9i Recovery Manager Reference for CHANGE syntax

  
  
• Automatic Control File Backup and Restore

  If you set CONFIGURE CONTROLFILE BACKUP to ON, then RMAN makes a mandatory and automatic control file autobackup after you run the BACKUP or COPY command. RMAN gives this backup a default name (which you can change using CONFIGURE CONTROLFILE BACKUP FORMAT), thereby allowing RMAN to restore this control file even in a disaster scenario in which the recovery catalog and current control file are lost.

  See Also: "Control File and Server Parameter File Autobackups" for concepts

  
  
• Block Media Recovery

  Block media recovery can perform media recovery on individual blocks in a datafile while the datafile remains online. The V$DATABASE_BLOCK_CORRUPTION view displays corrupt blocks in the most recent backup or image copy of each datafile.

  See Also: "Block Media Recovery with RMAN" for concepts, and Oracle9i Recovery Manager Reference for BLOCKRECOVER syntax

  
  
• Archived Redo Log Improvements

  RMAN enhances its treatment of archived redo logs in the following ways:

  • The BACKUP ... PLUS ARCHIVELOG command switches out of and archives the current online log, backs up archived logs, then performs another log switch and backs up remaining logs. This operation guarantees that the backed up datafiles can be recovered to a consistent state.
  • At the beginning of a backup of archived logs, RMAN automatically switches out of and archives the current online redo log if needed.
  • RMAN does not issue an error if a BACKUP ARCHIVELOG command does not discover any logs to back up.
  • RMAN performs archived log failover automatically. If RMAN discovers a corrupt or missing log during a backup, then it considers all logs listed in the repository as alternative candidates for the backup.
  • The DELETE ALL INPUT option of the BACKUP ARCHIVELOG command deletes all logs that match the specified criteria. In this way, you can delete logs located in multiple archiving destinations.
  • The BACKUP_COUNT column in V$ARCHIVED_LOG shows the number of times that a specified archived log was backed up.

    See Also: "Backups of Archived Logs" for concepts, and Oracle9i Recovery Manager Reference for BACKUP syntax

  
  
• LIST Enhancements

  The LIST command syntax is now more similar in structure to the CHANGE, CROSSCHECK, and DELETE commands. You also have more control over how the LIST output is displayed.

  See Also: "LIST Command Output" for concepts, and Oracle9i Recovery Manager Reference for LIST syntax

  
  
• CROSSCHECK Enhancements

  The functionality of the CROSSCHECK command is expanded, and the CHANGE ... CROSSCHECK is deprecated. The CROSSCHECK command is now similar in syntax to the DELETE and CHANGE commands.

  See Also: "Crosschecks of RMAN Backups and Copies" for concepts, and Oracle9i Recovery Manager Reference for CROSSCHECK syntax

  
  
• CHANGE Enhancements

  The CHANGE command can make files available or unavailable, catalog or uncatalog them, and change the KEEP setting, regardless of whether the backup repository is the control file or recovery catalog (except for CHANGE ... KEEP FOREVER, which requires a catalog). The CHANGE command operates on more types of files, and is now similar in syntax to the DELETE and CROSSCHECK commands.

  See Also: "Changes to Availability of RMAN Backups and Copies" for concepts, and Oracle9i Recovery Manager Reference for CHANGE syntax

  
  
• DELETE Enhancements

  The DELETE command combines the functionality of the previous CHANGE ... DELETE and DELETE EXPIRED commands. Additionally, you can run DELETE OBSOLETE to remove all files that are no longer needed. The DELETE command is now similar in syntax to the CHANGE and CROSSCHECK commands.

  Note that by default, DELETE EXPIRED and DELETE OBSOLETE prompt for confirmation before deleting files. In releases prior to Oracle9i, RMAN did not prompt when you ran DELETE EXPIRED.

  See Also: "Deletion of RMAN Backups and Copies" for concepts, and Oracle9i Recovery Manager Reference for DELETE syntax

  
  
• Backup of Backup Sets

  You can now back up backup sets from disk to tape or from disk to disk. If RMAN discovers a corrupt block or missing backup piece during the backup, then RMAN automatically performs failover to an existing intact copy.

  See Also: "Backups of Backup Sets" for concepts, and Oracle9i Recovery Manager Reference for BACKUP syntax

  
  
• Enhanced Duplexing Functionality

  You can specify up to four different FORMAT strings when generating a backup set, so each duplexed copy can have a different filename.

  You can enable duplexing by specifying the COPIES parameter on the following commands: CONFIGURE, SET, and BACKUP.

  See Also: "Duplexed Backup Sets" for concepts Oracle9i Recovery Manager Reference for BACKUP syntax Oracle9i Recovery Manager Reference for CONFIGURE syntax Oracle9i Recovery Manager Reference for SET syntax

  
  
• Backup Optimization

  You can configure RMAN to skip backups of files that have already been backed up. In this way, you can avoid making multiple backups of unchanging files such as archived logs. You can override this functionality with the FORCE option of the BACKUP command.

  See Also: "Backup Optimization" for concepts, and Oracle9i Recovery Manager Reference for CONFIGURE syntax

  
  
• Restartable Backups

  You can specify the NOT BACKED UP SINCE clause on the BACKUP command to back up only those files that were not backed up after a specified time. Hence, if a backup fails partway through, you can restart it and back up only those files that were not previously backed up.

  See Also: "Restartable Backups" for concepts, and Oracle9i Recovery Manager Reference for BACKUP syntax

  
  
  
  
• Restore Optimization

  When RMAN is restoring files, it checks the files on disk to determine whether a restore is necessary. If not, it does not restore the file. Hence, if a restore fails partway through, you can restart it and restore only those files that were not previously restored. You can override this behavior with the FORCE option.

  See Also: "Restore Optimization" for concepts, and Oracle9i Recovery Manager Reference for RESTORE syntax

  
  
• Multiple Block Size Support

  Oracle allows different tablespaces in a database to use different block sizes. RMAN backs up tablespaces with different block sizes in the same BACKUP command, but it never mixes datafiles with different block sizes in a single backup set. Each backup set contains only files with a single block size.

• Exclusion of Tablespaces From Backups

  You can configure RMAN so that a specified tablespace is excluded from whole database backups.

  See Also: "Configuring Tablespaces for Exclusion from Whole Database Backups" for concepts, and Oracle9i Recovery Manager Reference for CONFIGURE syntax

  
  
• NOCATALOG Mode Is Default

  If you do not specify either CATALOG or NOCATALOG on the command line, and if you do not run CONNECT CATALOG at the prompt, then RMAN defaults to NOCATALOG mode when you run a command requiring a repository.

  See Also: "Starting RMAN Without Connecting to a Database" for concepts

  
  
• RMAN Message Output Improvements

  The RMAN prefix is removed from non-error messages.

• SBT Library Architecture

  On platforms that support third-party media managers through the Oracle Media Management (SBT) API, the new SBT_LIBRARY parameter controls which media management library that RMAN uses on channels of DEVICE TYPE sbt. Use SBT_LIBRARY in the PARMS setting of the ALLOCATE CHANNEL or CONFIGURE CHANNEL command to specify the filename of the shared library to be loaded. You can also specify SBT_LIBRARY=oracle.disksbt, which causes the server to load Oracle's disk sbt library (formerly called the "dummy API").

  If no SBT_LIBRARY parameter is specified in PARMS, then the Oracle server attempts to load the dynamic libraries orasbt.dll on Windows NT and libobk.so on UNIX. If Oracle cannot locate the library, then the server returns an error.

  See Also: "Configuring RMAN to Make Backups to a Media Manager" to learn about linking to a media manager, and Oracle9i Recovery Manager Reference for PARMS syntax

Oracle8i New Features in Recovery Manager

The Oracle8i features and enhancements described in this section profoundly expanded the 8.0 RMAN functionality. Some of these features were not in all Oracle8i releases.

• 
  
• RMAN Support for Standby Database

  In release 8.1.7, you can use RMAN to create and back up a standby database.

  See Also: Chapter 13, "Creating a Standby Database with Recovery Manager"

  
  
• Making Test Backups

  In Oracle8i release 3 (8.1.7), the BACKUP VALIDATE command tests a backup without actually producing output files.

  See Also: "Test Backups Using RMAN" for concepts, and Oracle9i Recovery Manager Reference for syntax

  
  
• Setting the Default Location of the RMAN Snapshot Control File

  In Oracle8i release 3 (8.1.7), you can use the SET SNAPSHOT CONTROLFILE LOCATION TO DEFAULT command to set the default filename that is used for the snapshot control file. This default value is platform-specific and depends on the location of the Oracle home.

• Crosschecking and Deleting on Multiple Channels

  In Oracle8i release 3 (8.1.7), you can allocate multiple maintenance channels before issuing RMAN maintenance commands. RMAN checks on all channels that have the same device type as the channel used to create the backup.

  See Also: "Allocation of Multiple Channels for RMAN Maintenance Commands"

  
  
• Fewer Maintenance Commands Require a Catalog

  In Oracle8i release 3 (8.1.7), fewer maintenance commands require the use of a recovery catalog. The only options of the CHANGE command that require a recovery catalog are the following:

  • CHANGE ... AVAILABLE (note that backup sets, backup pieces, and proxy copies do not require the use of a recovery catalog)
  • CHANGE ... UNAVAILABLE

  The CROSSCHECK and DELETE EXPIRED commands no longer require a recovery catalog in release 8.1.7.

• Setting Recovery Catalog Compatibility Level No Longer Required

  In Oracle8i release 2 (8.1.6), the CONFIGURE COMPATIBLE command set the compatibility level in the recovery catalog. This command helped to solve problems resulting from the way in which RMAN updated and deleted catalog records. These problems are solved in Oracle8i release 3 (8.1.7), so the CONFIGURE COMPATIBLE command is still accepted for compatibility, but has no effect.

• Automatic Location of Backups on Oracle Real Application Cluster Nodes

  In Oracle8i release 2 (8.1.6), the AUTOLOCATE option of the SET command automatically discovers which nodes of an Oracle Real Application Clusters configuration contain the backups that you want to restore.

  See Also: Oracle9i Recovery Manager Reference for SET syntax

  
  
• Recovery Catalog Compatibility Setting

  In Oracle8i release 2 (8.1.6), the CONFIGURE COMPATIBLE command controls the compatibility of the recovery catalog packages with the RMAN executable.

• ALTER DATABASE RESETLOGS Command

  In Oracle8i release 2 (8.1.6), the RESETLOGS option of the ALTER DATABASE command opens the database and reset the online redo logs.

  See Also: Oracle9i Recovery Manager Reference for ALTER DATABASE syntax

  
  
• Deletion Commands Remove Repository Records

  In Oracle8i release 2 (8.1.6), the CHANGE ... DELETE, DELETE EXPIRED, and BACKUP ... DELETE INPUT commands can now remove catalog records rather than update them to status DELETED.

• Version 2.0 of the Media Management API

  Oracle releases the Media Management API, Version 2.0. Support for the version 1.1 Media Management API is maintained. The following are features of the new API:

  • Through an enhancement called proxy copy, the media management vendor software is able to take over data movement involved in a backup or restore.
  • Some media management software allows backup media to be arranged into storage pools based on media type, retention period, or other criteria. The POOL parameter of the BACKUP command provides integration between such products and RMAN.
  • When a channel is allocated, RMAN displays in its log a message identifying the media management product used to take backups on that channel. When the media manager encounters an error, it returns an error message explaining the error, which is displayed in the RMAN log.
  • The SEND command allows commands to be sent directly from an RMAN session to the media management software.

    See Also: Oracle9i Recovery Manager Reference for BACKUP syntax and see Oracle9i Recovery Manager Reference for SEND syntax

  
  
• Crosscheck and Delete Functionality

  The commands CROSSCHECK BACKUP, CHANGE ... CROSSCHECK, and DELETE EXPIRED BACKUP allow for the synchronization of the recovery catalog with the media manager's catalog. RMAN can determine whether backups and copies are on disk or tape and update their repository record if they are not.

  See Also: Oracle9i Recovery Manager Reference for CHANGE syntax Oracle9i Recovery Manager Reference for CROSSCHECK syntax Oracle9i Recovery Manager Reference for DELETE syntax

  
  
• Improved LIST Output

  The output of the LIST BACKUP command now prints the list of backups belonging to a backup set in a separate section of the report from the list of data files or archived logs included in the backup set.

  See Also: Oracle9i Recovery Manager Reference for LIST syntax

  
  
• Reports on Needed Backups

  A new command, REPORT NEED BACKUP REDUNDANCY, alerts the user that a new backup is required when fewer than a user-specified number of backups of a datafile exist.

  See Also: Oracle9i Recovery Manager Reference for REPORT syntax

  
  
• CREATE CATALOG Command

  The CREATE CATALOG command creates the recovery catalog. It replaces catrman.sql and associated scripts in the ?/dbs/admin directory.

  See Also: Oracle9i Recovery Manager Reference for CREATE CATALOG syntax

  
  
• UPGRADE CATALOG Command

  Previously it was necessary to run a SQL script to perform a recovery catalog upgrade. Now you can upgrade the catalog with the UPGRADE CATALOG command.

  See Also: Oracle9i Recovery Manager Reference for UPGRADE CATALOG syntax

  
  
• DROP CATALOG Command

  The DROP CATALOG command removes the recovery catalog schema.

  See Also: Oracle9i Recovery Manager Reference for DROP CATALOG syntax

  
  
• STARTUP, SHUTDOWN, and ALTER DATABASE Commands

  The RMAN commands STARTUP, SHUTDOWN, and ALTER DATABASE (MOUNT and OPEN options only) have the same syntax as their equivalent SQL*Plus commands.

  See Also: Oracle9i Recovery Manager Reference for STARTUP syntax Oracle9i Recovery Manager Reference for SHUTDOWN syntax Oracle9i Recovery Manager Reference for ALTER DATABASE syntax

  
  
• Database Duplication

  The DUPLICATE command allows creation of a new database using the backups of another database.

  See Also: Chapter 12, "Duplicating a Database with Recovery Manager"

  
  
• Disk Affinity in Oracle Real Application Clusters

  When backing up on multiple nodes of an Oracle Real Application Clusters configuration, it is possible that some disks have affinity to certain nodes in the cluster such that access to those disks is faster from those nodes than from other nodes in the cluster. RMAN recognizes node affinity, if it exists, and attempts to schedule datafile backups on channels allocated at nodes that have affinity to those files.

• Duplexed Backups

  RMAN can create up to four concurrent copies of each backup piece.

  See Also: "Duplexed Backup Sets"

  
  
• RMAN-Generated Backup Piece Names

  RMAN no longer requires that backup piece names be explicitly specified using the FORMAT parameter. By default, RMAN chooses a unique name for each backup piece.

• Backup Pieces Not Overwritten

  A backup piece is no longer overwritten if an attempt is made to create a backup piece with the same name as an existing one. Instead, RMAN issues an error message.

• TSPITR Does Not Require a Catalog

  You can perform TSPITR (Tablespace Point -in-Time Recovery) without a recovery catalog.

  See Also: "Performing TSPITR Without a Recovery Catalog"

  
  
• New V$ Views for Monitoring Backup Performance

  Two new views are available to monitor the progress and performance of Recovery Manager backups: V$BACKUP_SYNC_IO and V$BACKUP_ASYNC_IO.

  See Also: "Step 8: Query V$ Views to Identify Bottlenecks"