Recover a missing or corrupted pluggable database when:
-
A pluggable database is corrupted after you have restored the container database
-
A pluggable database is the only lost data that must be restored. You can restore the pluggable database instead of the entire container database.
Note
Due to an Oracle limitation, if you choose to recover pluggable databases to a point-in-time, or to a SCN, then you must separate the tasks into multiple RMAN commands so that each command operates on a single PDB. For more information, see Viewing Oracle Restore RMAN Scripts and Customizing Oracle Restore RMAN Scripts.
Before You Begin
-
Perform a full backup, or an incremental backup with a subclient configured for Oracle pluggable databases.
-
Place the pluggable databases you want to restore in OFFLINE mode, or set the Commvault software to automatically move the database to the correct mode before the restore.
Procedure
-
From the CommCell Browser, expand Client Computers > client > Oracle.
-
Right-click the instance, point to All Tasks and then click Browse and Restore.
-
In the Browse and Restore Options dialog box, select the backup to use for the clone:
-
To create the clone from the latest backup, select Latest Backup and click View Content.
-
To create the clone from a point-in-time backup, make the following selections:
-
Select Time Range and then select Absolute Time.
-
Select the Time Zone, then select End Time.
-
In the End Time area, select or enter the date and time.
-
Click View Content.
Note
To recover a dropped PDB, set the End Time to the most recent backup time when the PDB existed.
-
-
-
From the browse window, select the database in the left pane, then select the PDBs to restore in the right pane. 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 of the Oracle Restore Options dialog box, click Advanced.
The Advanced Restore Options dialog box appears.
-
To set the Commvault software to automatically move the database to the correct mode before the restore, on the options tab, 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.
Configure 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.
-
-
On the Recover tab, select the database recover option:
Choice
Description
Current Time
Recover to the current time.
Point-in-Time
-
Enter the date and time.
Note: If the time zone is different on the CommServe computer and client, in the Time Zone box, select the client computer time zone.
-
Specify the staging path. On the Auxiliary Instance tab, in the Staging Path box, type the full path to the location where the software creates the auxiliary instance.
SCN
The System Change Number (SCN) tracks the timing of transactions in the Oracle database. The SCNs are stored in the control files and the datafile headers. You can recover the database to the last existing SCN number in the control file, which is the last consistent database state.
Latest Backup Time
Recover to the latest backup job's completion time, which gets passed to the recover operation.
This value is the Completion Time on the General Tab of the Job Details dialog box. To view the value, right-click the job, and then select View Job Details. For instructions, see Job Controller - Getting Started.
Latest SCN Number
Recover to the latest SCN.
The latest backup job's Next SCN number is passed to the recover operation. This is the Next SCN on the General Tab of the Job Details dialog box. To view the value, right-click the job and then select View Job Details. For instructions, see Job Controller - Getting Started.
Relative to System Date
Recover to the number of days or hours relative to the current system date. The default option is to recover relative to the days,.
If you select the Days option, the valid values are 0-7.
If you select the Hours option, the valid values are 0-23.
-
-
If you chose to restore to a point-in-time, then on the Auxiliary Instance tab, in the Staging Path box, type the complete path to the staging path.
-
Click OK to close the Advanced Restore Options dialog box.
-
Optional: You can 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.