You can restore archive logs separately or in addition to the database. You can use the procedure on this page or use a CLI tool. For more information about the CLI tool, see Restoring Oracle Archive Logs with a CLI Tool.
Restore an archive log when you are restoring any of the following data items:
-
A database to the most recent good, backed up state, after a database failure has occurred.
-
Specific logs which are identified using a serial number or identification tag, that are missing in the database.
-
Logs from a specific time range that were lost due to a hard disk corruption. You can use a point-in-time option to restore the archive logs.
Before You Begin
Optional: When the backup pieces are unknown to the RMAN repository, catalog the backup pieces. For more information, see Cataloging RMAN Backup Pieces.
Procedure
-
From the CommCell Browser, expand Client Computers > client > Oracle.
-
Right-click the instance, point to All Tasks, and then click Browse and Restore.
-
On the Browse and Restore dialog box, select Latest Backup and click View Content.
-
Optional: Use non-default Browse and Restore options. See Browse and Restore.
-
From the Browse window, select the data to restore in the right pane and click Recover All Selected.
-
Depending on the type of restore to be run, click Restore in place or Restore out of place, and then click Next.
The Oracle In Place Restore Options or Oracle Out of Place Restore Options dialog box appears.
-
On the Oracle Restore Options dialog box:
-
Select the Restore Archive Log check box.
-
To restore the log files without the database, clear the Restore Data check box.
-
Click Advanced.
The Advanced Restore Options dialog box appears.
-
-
On the Restore tab, select the restore log option.
Restore all logs
Select the All option
Restore logs by a specific log time
Select By Log Time and enter the Start and End time in the boxes.
If you only specify the start log time and not the end log time, the system restores all logs from the start time to the current time.
If the restore includes the database, see Restoring an Oracle Database to a Point-in-Time.
Restore by specifying a tag
Select the By Tag check box and type the tag in the By Tag box.
Restore by specifying a serial number
Select the By Log Serial Number option.
Check the Start or End check boxes and enter the serial numbers.
The following are the rules for specifying the serial number.
-
The end serial number must be greater than or equal to the start serial number
-
The start and the end serial number cannot be 0
-
The range of serial numbers restore can be from one or more backup jobs or from a part of a job and from one or more cycles
-
When you specify only the start sequence number, logs starting from that sequence number to the current sequence number are restored
-
-
To restore logs to a different location from the original location, enter the new path in the Target Directory box.
-
To set the Commvault software to automatically move the database to the correct mode before the restore, select the Switch Database Mode for Restore check box.
-
Optional: Select the restore options.
Set the Oracle Database ID
The Oracle DBID is an internal, uniquely generated number that distinguishes the target database from the rest of the databases with the same name, in the recovery catalog. Oracle creates this number automatically when you create the database.
You can use this option when:
-
There is no recovery catalog and you need to restore the control file or SP file from the autobackup
-
Multiple databases exist in the recovery catalog and you need to restore the control file
On the Options tab, select the Set DBID check box.
Reset the database and logs.
By default, the database is automatically set to open, and the logs are reset.
If you reset the logs to an open state, you can then reset the database.
On the Options tab, select the Reset Database check box and one of the following Reset Log options:
-
To open the database without the RESETLOGS option, select None.
-
To open the database with the RESETLOGS option, select Yes.
-
To open the database with the NORESETLOGS option, select No.
Perform a point-in-time restore of a database that was backed up in NOARCHIVELOG mode
If the database was backed up in NOARCHIVELOG mode, enable the redo logs.
When the no redo log is disabled, RMAN searches archived redo logs after applying the incremental backup data during a restore. When you set No Re-do Logs, RMAN restores the data from the incremental backup and not the archived redo logs.
On the Options tab, select the No Re-do Logs check box.
Prevent RMAN failovers to the previous backup for Oracle 10g databases or higher
Select this option if you want to increase the speed.
During restore operations, RMAN automatically looks for another copy of the backup file under the following circumstances:
-
A backup piece is corrupted or deleted
-
A MediaAgent is offline
-
A block in the backup is corrupted within the latest full backup
If another copy is not available in the other copy, RMAN uses an older version of the file. When multiple channels are available for the same device type, RMAN automatically retries on another channel and searches all prior backups until it has exhausted all possibilities.
On the Options tab, select the Disable Oracle Channel Restore Failover check box.
Validate the restore
Validation verifies that the backup copies of the data and logs are intact and usable for restores. RMAN simulates the restore job without the media to determine whether the restore can be successfully performed.
When a validate job is complete, you can view the job log files to identify and correct any issues.
On the Options tab, select the Validate check box.
Configuring Pre- and Post-Processes
Run scripts before or after the restore.
Enter the full path for the pre-recovery and post-recovery script.
You can choose to run the post-process script even if the restore job failed. You can use the post-process script to bring a database online or to release a snapshot.
To pass the database instance name to the script, see Passing the Instance Name to Pre and Post Scripts for Databases.
On the Pre/Post tab:
-
In the Pre-Recovery Command box, type the full path name for the script.
-
In the Post-Recovery Command box, type the full path name for the script.
-
To run the post recovery process regardless of the job's outcome, select the Run Post Process for all attempts check box.
-
In Windows configurations, specify the user that runs the process, in the Pre/Post Impersonation section, select one of the options:
if the local account has permission to execute the processes on the destination client, select the Use Local Accounts option.
To impersonate another user with permission, select the Impersonate User option and enter the credentials.
Restore from a copy precedence
If the backup is corrupted, restore from a storage policy copy instead of the backup.
For more information on modifying the copy precedence of a storage policy copy, see Copy Precedence.
On the Copy Precedence tab, select the Restore from Copy Precedence number check box and enter a copy precedence number.
Restore from a specific backup
On the Restore tab, select the By Tag check box and enter the tag.
Open the database after the restore
After a restore, set the Commvault software to automatically open the Oracle database. When the database is open, it records transactions.
On the Options tab, select the Open DB check box.
Reset the database and logs.
By default, the database is automatically set to open, and the logs are reset.
If you reset the logs to an open state, you can then reset the database.
On the Options tab, select the Reset Database check box and one of the following Reset Log options:
-
To open the database without the RESETLOGS option, select None.
-
To open the database with the RESETLOGS option, select Yes.
-
To open the database with the NORESETLOGS option, select No.
-
-
Click OK to close the Advanced Restore Options dialog box.
-
Optional: View or customize the RMAN script that is automatically generated from the selected options. For more information, see Viewing Oracle Restore RMAN Scripts and Customizing Oracle Restore RMAN Scripts.
-
Click OK to close the Restore Options dialog box and start the restore.