Chatta subito con l'assistenza
Chat con il supporto

NetVault Plug-in for Oracle 11.2 - 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 Troubleshooting

Finalizing and submitting the job

Complete the steps outlined in Finalizing and submitting the job under Performing User Managed restores.

Using RMAN types of recovery in a non-RAC environment

The following topics describe the types of recovery that you can perform in a non-RAC environment:

For information on the types of RMAN recoveries available in a RAC environment, see Restoring data in a RAC environment.

Restoring the Control File from an Autobackup

Restoring the Control File should only be performed in the following cases:

Oracle® Customer Support has advised that a Control File restore is required.

As the Autobackup uses a default format, RMAN can restore it even if it does not have a repository available that lists the available backups. RMAN replicates the Control File to all CONTROL_FILES locations automatically.

3
Use SET DBID to set the database identifier for the target database.
SET DBID <Source_DBID>;
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.

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:

1
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.
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:
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.
4
Complete the Target Client, Schedule, and Advanced Options tabs, and submit the job.
Related Documents

The document was helpful.

Seleziona valutazione

I easily found the information I needed.

Seleziona valutazione