Restoring the Control File should only be performed in the following cases:
3 |
Use SET DBID to set the database identifier for the target database. |
This type of recovery is performed when the database is open, but some of the datafiles are damaged. This recovery is useful when you want to recover the damaged tablespace, while leaving the database open so that the rest of the database remains available. You can only perform Complete Recovery when restoring and recovering individual datafiles or tablespaces. PIT Recovery is not available for individual datafiles or tablespaces. Enabling PIT Recovery causes the restore job to fail. Following is an overview of the process to recover individual datafiles or tablespaces:
1 |
On the Create Selection Set page, select the damaged datafiles or tablespaces from the latest available backup of the tablespace, and click . |
2 |
Click the Restore Options tab, and select the Alter Tablespaces Offline Before Restore and the Alter Tablespaces Online After Restore options. |
3 |
On the Perform Recovery tab, select the applicable options: |
• |
• |
If you do not want to perform any recovery, select the Do Not Perform Recovery option. |
• |
To delete the restored archive logs that Oracle deems unnecessary, select the Delete Restored Archive Logs No Longer Needed option. |
4 |
1 |
On the Create Restore Job — Choose Saveset page, find the latest available backup that included all the tablespaces, and click Next. |
2 |
On the Create Selection Set page, navigate to the source NetVault Client and database, select the Whole Database node, and click . |
3 |
Click the Restore Options tab, and select the applicable options: |
• |
To mount the database before the performing the restore, select Mount Database Before Restore. |
• |
To shut down the database automatically before mounting the database, select Shutdown Abort Database First. |
• |
To include read-only datafiles in the restore, select Check Read-Only Datafiles and Restore if Necessary. |
4 |
• |
Perform Complete Recovery: Recovers the database to the current time, that is, to the last committed transaction available in the archived and online redo logs. |
• |
Perform Point-in-Time Recovery: Recovers the database to a specific point whether it be a specific time, log sequence number, or SCN. |
5 |
On the Perform Recovery tab, select these additional options, if applicable: |
• |
To include read-only datafiles in the recovery process, select Check Read-Only Datafiles and Recover if Not Current. The read-only files are included only if they are needed to complete recovery. If they are not damaged, RMAN omits them. |
• |
To delete the restored archive logs that Oracle deems unnecessary, select Delete Archive Logs No Longer Needed. |
6 |
On the Post Recovery tab, select Open Database after Recovery and Read Write and Reset Logs to open the database automatically in read-write mode and reset the online logs. |
7 |
If your goal is to create a copy of your target database for ongoing use on a new host, do not use these procedures. Instead, use the Duplicate Database backup type, which is designed for this purpose. For more information, see Duplicate Database backup.
The following methods are available for performing a disaster recovery:
When performing a disaster recovery of any kind, be aware of the following:
© ALL RIGHTS RESERVED. Terms of Use Privacy Cookie Preference Center