Chat now with support
Chat with Support

NetVault Plug-in for Oracle 12.3 - User Guide

Introducing Quest® NetVault® Backup Plug-in  for Oracle Defining a backup strategy Installing and removing the plug-in Configuring the plug-in Backing up data Using the Oracle Flashback Database Restoring data
Restoring and recovering data: an overview Performing User Managed restores Using advanced User Managed restore procedures Performing RMAN restores Using RMAN types of recovery in a non-RAC environment Using advanced procedures with RMAN restores
Maintaining the Recovery Catalog Using the RMAN CLI Using the plug-in with Oracle RAC Using the plug-in in a failover cluster environment Using the plug-in with Oracle Data Guard Using the plug-in with Oracle Container Databases (CDBs) and Pluggable Databases (PDBs) Troubleshooting

Determining which datafiles require recovery

When a media failure or data corruption has occurred, you can use the following SQL*Plus query to determine which datafiles need recovery. This command works only when the database is in an OPEN state:

Recovering datafiles and archive logs

After identifying the damaged datafiles, restore the last Full Backup of the datafiles and the backup of all archive logs generated since the last backup until the target recovery time. When you restore the datafiles, the existing files are replaced with the backed-up copy. Conversely, when you restore the archive logs, these files are copied to the original location so that they are available to the database during the recovery process.

The recovery of the damaged datafiles and the archive logs includes the following steps:

Restore the logs to the primary destination directory. If space is limited, use the Rename option to restore the logs to a different directory. For more information, see Using advanced User Managed restore procedures.
After the restoration is complete, use SQL*Plus to perform the recovery manually by issuing the following command for every tablespace that needs recovering:

Restoring Control Files

You can recover a Control File using one of the following options:

Restoring a Lost Copy of a Multiplexed Control File: Use this procedure to recover a database if a permanent media failure has damaged one or more Control Files of a database, and at least one Control File has not been damaged by the media failure. For more information, see Restore Lost Copy of a Multiplexed Control File in the Oracle Database Backup and Recovery Advanced User’s Guide or to Responding to the Loss of a Subset of the Current Control Files in the Oracle Database Backup and Recovery User’s Guide for Oracle 11g.
Restoring a Control File from Backup After Loss of All Current Control Files: Use this procedure to restore a Backup Control File if a permanent media failure has damaged all Control Files of a database and you have a backup of the Control File.

When a Control File is inaccessible, you can start the Instance, but not mount the database. If you attempt to mount the database when the Control File is unavailable, you get the following error message:

You cannot mount and open the database until the Control File is accessible.

The plug-in saves a copy of the snapshot of the Control File to the Control File Save Filename (Full Path) specified on the Add, or Edit, Oracle Database dialog box. You can copy the Control File from this location if you lose all current Control Files. If the snapshot is not available in the Control File Save Filename (Full Path), you can restore it from the backup by performing the following steps:

The plug-in restores it to the Control File Save Filename (Full Path). The restored file has a “.SAV” extension.
For more information on restoring a Backup Control File, see Restoring a Backup Control File to the Default Location in the Oracle Database Backup and Recovery Advanced User’s Guide.

Understanding RMAN recovery

Review the following topics regarding RMAN recovery:

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating