NetVault Plug-in for Oracle 12.3

Running the ALTER DATABASE OPEN RESETLOGS command from RMAN versus SQL*Plus resets the target database automatically so that you do not have to run a RESET DATABASE. By resetting the database, RMAN considers the new incarnation as the current incarnation of the database. If you run ALTER DATABASE OPEN RESETLOGS from SQL*Plus and do not follow it with a RESET DATABASE at the RMAN prompt, RMAN refuses to access the Recovery Catalog. RMAN refuses because it cannot distinguish between a RESETLOGS operation and an accidental restore of an old Control File.


	IMPORTANT: After restoring the Control File from an Autobackup, Quest recommends that you perform a Full or Incremental Level 0 backup with the database node selected on the NetVault Backup Selections page.

Recovering individual datafiles and tablespaces to the same server

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:

On the Create Selection Set page, select the damaged datafiles or tablespaces from the latest available backup of the tablespace, and click Edit Plugin Options.

Click the Restore Options tab, and select the Alter Tablespaces Offline Before Restore and the Alter Tablespaces Online After Restore options.

On the Perform Recovery tab, select the applicable options:

•

To recover the tablespace to the current time, that is, last committed transaction available in the archive and online redo logs, select the Perform Complete Recovery option.

•

If you do not want to perform any recovery, select the Do Not Perform Recovery option.


	NOTE: If you select the Perform Database Point in Time Recovery option, the restore job fails.

•

To delete the restored archive logs that Oracle deems unnecessary, select the Delete Restored Archive Logs No Longer Needed option.

Complete the Target Client, Schedule, and Advanced Options tabs, and submit the job.

RMAN automatically chooses the best available Full, Incremental, or Archive Log backups and restore and recover the tablespace.

Recovering Whole Database to same server

This type of recovery is performed when the current Control File and SPFILE are intact but all the datafiles are damaged or lost. You can perform a Complete Recovery or recover the database to a specific point. Following is an overview of the process to recover the whole database, which must be performed when the database is in a MOUNT state:

On the Create Restore Job — Choose Saveset page, find the latest available backup that included all the tablespaces, and click Next.

On the Create Selection Set page, navigate to the source NetVault Backup Client and database, select the Whole Database node, and click Edit Plugin Options.

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.

To perform recovery on the database, that is, to reconstruct the database up to the current or specified point, select one of the following options on the Perform Recovery tab:

•

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.

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.

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.

Complete the Target Client, Schedule, and Advanced Options tabs, and submit the job.

RMAN automatically chooses the best available full, incremental, or Archived Log backups and restore and recover the database.


	IMPORTANT: After completing a restore of the Whole Database, Quest recommends that you perform a Full or Incremental Level 0 backup with the database selected on the Create Selection Set page.

Performing disaster recovery with RMAN

Disaster recovery includes the restore and recovery of a database after the loss of the entire target database, all current Control Files, all online redo log files, and all parameter files. It is also assumed that the FRA has been lost. To perform a disaster recovery, the minimum required set of backups includes backups of all the datafiles, some archived redo logs generated after the time of the backup, and at least one Autobackup of the Control File.

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.


	CAUTION: To avoid overwriting the database and losing data, use caution when selecting any of the options described in the following topics and before performing disaster recovery.