Specifies the highest sequence number for the control file autobackup search. If the initialization parameter DB_BLOCK_CHECKSUM=TRUE, and if MAXCORRUPT and NOCHECKSUM are not set, then specifying CHECK LOGICAL detects all types of corruption that are possible to detect. If no suitable backups are available in the current incarnation of the database, then you can force RMAN to use backups from a previous incarnation. If you restore to the default location (that is, you do not run SET NEWNAME), then RMAN overwrites files with the same filenames. See Also: "BACKUP" for a description of how a tag can be applied to an individual copy of a duplexed backup set, and for a description of the default filename format for tags. Only use with catalog for testing purposes. RMAN only restores backups that were created on the same type of channels that are allocated for the RESTORE command. If you use the FROM DATAFILECOPY option, then the allocated channels must be of DEVICE TYPE DISK. PREVIEW operation again to see if RMAN selects another remote backup. The output of RESTORE identifies such backups, if the media manager provides the necessary information. Use, Specifies the objects to be restored. See Also: "Restrictions and Usage Notes for the SET DBID Command". Specify UNTIL or TAG options of RESTORE to restore older versions of the server parameter file. For example, the following command is illegal because datafile 1 is both specified explicitly and implied by the SYSTEM tablespace: You must have already configured a device type by using CONFIGURE (except for DISK, which is preconfigured) before specifying the DEVICE TYPE option. Restoring Files in a Real Application Cluster Configuration. If no autobackup is found within MAXDAYS days, then RMAN signals an error and the command stops. First run SET DBID. The DROP option indicates that RMAN does not intend to recover these files and intends to drop their tablespaces from the database after the database is opened again. If both the primary and standby databases are known to the recovery catalog, then the configuration settings for both databases are recorded in the recovery catalog. For password-mode encrypted backups, the required passwords must be provided using SET DECRYPTION. No catalog, target started in NOMOUNT state. If you do not run SET NEWNAME and RMAN detects that the default filename cannot be used (for example, because the filename is in use by another database that shares the storage), and if the file is an Oracle Managed File or is on an Automatic Storage Management disk group, then RMAN attempts to create a new file in the same location or disk group. Specifies the case-sensitive name of a channel to use for this restore operation. Table 2-27 indicates the restrictions that apply in different situations involving the RESTORE CONTROLFILE command. PREVIEW: ExampleThe following example shows the results of a RESTORE PREVIEW, which identifies the backupsets RMAN selects for use in restoring archivelogs from backup. Run STARTUP FORCE NOMOUNT before running RESTORE SPFILE (with FROM AUTOBACKUP if in NOCATALOG mode). Note that database restore and recovery has no user-visible effect on change tracking. Restores only to filename. PREVIEW again, periodically, to monitor whether the needed backups are stored locally again. See the reference entries for those commands for more details. Restores all datafiles in the specified tablespaces. Must specify FROM AUTOBACKUP. Copyright1996, 2005,Oracle. To restore other files, mount the database and then continue. For example, if channel 1 connected to instance 1 can read log 1000 from its tape drive, but channel 2 connected to instance 2 cannot read the same log from its tape drive, then channel 1 restores the log.

For an overview of the encrypted backups mechanism, a guide to its use and information on choosing among the different modes of encryption, see "Encryption of Backup Sets" and the extended discussion in Oracle Database Backup and Recovery Advanced User's Guide. If you are restoring the server parameter file and the control file in a disaster recovery situation, you cannot run RESTORE CONTROLFILE FROM AUTOBACKUP, mount this control file, and then run RESTORE SPFILE without the FROM AUTOBACKUP clause. If you specify the CHECK READONLY option, then RMAN examines the headers of all read-only datafiles and restores any that need restoring. The primary use of RESTORE is to restore files from backups or image copies. Because the RECOVER command automatically restores archived logs as needed, you should seldom need to restore logs manually. In the absence of any other criteria, RMAN selects the most current file copy or backup set to restore. If the server parameter file is lost, connect to the target (and catalog if used) and then run SET DBID. For example, you can limit the restore to backups before a given point of time (within the current incarnation) with the untilClause. Autolocation is automatically enabled when the channels meet any of the following criteria: To restore datafiles to their current location, the database must be started, mounted, or open with the tablespaces or datafiles to be restored offline. Provides a DB_NAME to be used in searching for control file autobackups. Note: You must always run the RECOVER command after restoring a control file, and must also always open the database with the RESETLOGS option. If you do not specify a channel, then, Restores a control file autobackup. Note: The database can be started, mounted, or open for this operation. To restore to a new location, run SET NEWNAME commands to rename the datafiles and SWITCH commands to make them the current database files. PREVIEW RECALL is used to request the recall of backups needed for a RESTORE operation that are stored on remote storage. RMAN does not support backup and recovery of the change tracking file. The RMAN CONFIGURE, SET and SHOW commands are used to manage the RMAN backup encryption settings for your database. With the DB_UNIQUE_NAME , RMAN is able to locate the correct configuration settings for the node on which the SPFILE is being restored, and can use them to access backup devices. PREVIEW with the RECALL option. Because the two databases have the same DB_NAME, the records in the recovery catalog can only be distinguished using the value of the DB_UNIQUE_NAME initialization parameter for the primary and standby databases. Tests data and index blocks that pass physical corruption checks for logical corruption, for example, corruption of a row piece or index entry. Overrides the default selection of the most recent backups or file copy available. It can, however, re-create locally managed temporary tablespaces after a database restore. Limits the search for a control file autobackup to within the specified number of days in the past. The tag restricts the automatic selection to backup sets or file copies that were created with the specified tag. On the first day searched, the search begins with sequence number 256 (or the sequence number specified by MAXSEQ, if provided) and counts back to sequence 0.

Restoring a Tablespace: ExampleThis example takes a tablespace offline, restores it, then performs media recovery: Restoring the Control File When Using a Recovery Catalog: ExampleThis example restores the control file to its default location, replicates it automatically to all CONTROL_FILES locations, and mounts the database: Restoring the Control File with a Tag: ExampleThis NOCATALOG example restores the control file specified by a tag, and then mounts the database: Restoring the Database with a Backup Control File: ExampleThis example restores the control file to a temporary location, replicates it to all control file locations specified in the CONTROL_FILES initialization parameter, and then restores and recovers the database: Restoring Archived Redo Logs to a New Location: ExampleThis example restores all archived redo logs to the /oracle/temp_restore directory: Restoring a Control File Autobackup to a Nondefault Location: ExampleThis example restores the latest control file autobackup made on or before June 23, 2000 with a nondefault format of PROD_CF_AUTOBACKUP_%F. Note: Using RESTORE SPFILE when the DB_NAME is not unique in the recovery catalog produces an RMAN-6758 error. RMAN detects that the tablespace has changed its name and updates the recovery catalog on the next resynchronization. If you do not specify, Specifies whether RMAN should restore from a, Limits the selection to backup sets or file copies that are suitable for a point-in-time recovery to the specified time. The. Allrightsreserved. If you restore to a new location, then issue SET NEWNAME commands to rename the files and issue a SWITCH command to make the restored files current. Restores from specified file. For transparent-mode encrypted backups, the required passwords must be available in the database wallet. See Oracle Database Backup and Recovery Advanced User's Guide for details on restore failover. If TO 'filename' not used, restores to all CONTROL_FILES locations. Specifies path to flash recovery area to search for autobackups. The translates the tablespace name internally into a list of datafiles. Do not specify a datafile more than once in a restore job. If multiple backup sets or file copies have a matching tag, then RMAN selects the most recent one. RMAN chooses which backups to restore based on the criteria that you specify. Some media managers provide status information to RMAN about which backups are vaulted, that is, stored in a remote location such as a secure storage facility, and which therefore cannot be used without retrieving media. (Note that in this output, one of the archivelog backups is stored remotely.). You cannot manually allocate channels and then run RESTORE DEVICE TYPE. By default RMAN restores the most current server parameter file. Restores the datafiles specified by filename or absolute datafile number. Typically, you restore when a media failure has damaged a current datafile, control file, or archived log or prior to performing a point-in-time recovery. RMAN can back up and restore dictionary-managed temporary tablespaces, but it cannot back up locally managed temporary tablespaces. Note: These parameters override the parameters with the same name at the RESTORE command level. You can only specify this option on the, Specifies the name of the control file copy or backup piece containing a control file. PREVIEW RECALL automatically requests the retrieval of the remotely stored backup media. During recovery, all archived logs back to the creation of the datafile will be restored, and all changes during the history of the datafile will be re-applied to re-create its contents. If you do not manually allocate channels, then RMAN allocates all automatic channels possibly needed by the RESTORE command, subject to any restrictions imposed by the use of the DEVICE TYPE option. If you rename a tablespace (for example, from users to customers), then so long as an additional tablespace with the old name (users) has not been created, you can use either the old name (users) or the new name (customers) for the tablespace. For dual-mode encrypted backups, the required passwords must be available in the database wallet or provided using SET DECRYPTION. In a Real Application Clusters configuration, RMAN automatically restores backups, control file copies, and datafile copies from channels that can read the files on tape or a local file system. If you do not issue SWITCH commands, then RMAN considers the restored files as valid copies for use in future restore operations. If the database is started but not mounted in NOCATALOG mode, then the RESTORE SPFILE command requires the FROM AUTOBACKUP clause. If any of these conditions is not met, then RMAN restores the fileswhether or not they are read-only. If TO 'filename' not used, restores to all CONTROL_FILES locations.