Restoring Oracle Individual Datafiles and Tablespaces

Recover a missing or corrupted datafile and tablespace in the following situations:

A datafile or tablespace is corrupted after you have restored the database.
A datafile or tablespace is the only lost data that must be restored. You can restore the datafile or tablespace instead of the entire database.

You must place the datafiles and tablespaces that you want to restore offline, before you start the restore. The database can remain online, unless you restore Oracle SYSTEM tablespaces.

When you perform a restore, the IntelliSnap ASM diskgroup is mounted and the data file copy is cataloged on the mounted ASM diskgroup. The restore uses RMAN scripts.

Before You Begin

Perform a full backup with a subclient configured for Oracle datafiles and tablespaces.
Place the tablespace you want to restore in OFFLINE mode, or set the Commvault software to automatically move the database to the correct mode before the restore.
```
ALTER TABLESPACE users OFFLINE IMMEDIATE
```

Procedure

From the CommCell Browser, go to Client Computers > client > Oracle.
Right-click the instance, then go to All Tasks > Browse and Restore.

The Browse and Restore Options dialog box appears.
Select Latest Backup, and then click the View Content button.
In the right pane of the CommCell Browser window, select the datafiles and tablespaces to restore, and then click Recover All Selected.

The Oracle Restore Options dialog box appears.
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 General tab, click Advanced.

The Advanced Restore Options dialog box appears.
On the Options tab, select the Switch Database Mode for Restore check 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 control file 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.
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.
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 Redo Logs, RMAN restores the data from the incremental backup and not the archived redo logs.

On the Options tab, select the No Redo 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.

Perform a point-in-time restore when the database is in NOARCHIVELOG mode

When you set this feature, RMAN restores only the data from the incremental backup and not the archived redo logs.

On the Options tab, select the No Redo Logs 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.

On the Pre/Post tab:
1. In the Pre-Recovery Command box, type the full path name for the script.
2. In the Post-Recovery Command box, type the full path name for the script.
3. To run the post recovery process regardless of the job's outcome, select the Run Post Process for all attempts check box.
4. 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.

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.
Click OK to close the Advanced Restore Options dialog box.
Click OK to close the Restore Options dialog box and start the restore.

If your restore includes Oracle SYSTEM tablespaces, switch the database mode to MOUNT.