Chat now with support
Chat with Support

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

Retrieving a Control File manually

When Control File Autobackups are not available, the RMAN Catalog is not used, and only Control File backups were performed by selecting the Control File node on the NetVault Backup Selections page, you might be able to use the following procedure to extract the Control File from a backup piece.

1
On the Create Restore Job — Choose Saveset page, find the latest available backup that is marked with “Controlfile Included.”
2
Recover the Control File.
SQL> STARTUP NOMOUNT;
DECLARE
devtype varchar2(256);
done    boolean;
BEGIN
devtype := dbms_backup_restore.deviceallocate('sbt_tape', params=>'');
dbms_backup_restore.restoresetdatafile;
dbms_backup_restore.restorecontrolfileto
('<destination PathAndNameOfControlFile>');
dbms_backup_restore.restorebackuppiece
('<backupSegment NameIdentifiedEarlier>',done=>done);
END;
/
For example:
sqlplus /nolog
connect / as sysdba
STARTUP NOMOUNT;
DECLARE
devtype varchar2(256);
done    boolean;
BEGIN
devtype := dbms_backup_restore.deviceallocate('sbt_tape', params=>'');
dbms_backup_restore.restoresetdatafile;
dbms_backup_restore.restorecontrolfileto
('C:\oracle\product\10.1.0\oradata\o10gg\control01.ctl');
dbms_backup_restore.restorebackuppiece
('ZETK2003:#3293:ZETK2003:274_578391288:O10GG_1135958971',done=>done);
END;
/
3
Use the replicate controlfile command to copy the restored Control File.
RMAN TARGET / NOCATALOG
SET DBID <Source_DBID>;
connect TARGET /
RUN {
ALLOCATE CHANNEL C1 TYPE 'SBT_TAPE';
replicate controlfile from
'<sourcePathAndNameOfControlFile>';
}

Using advanced procedures with RMAN restores

This topic contains subtopics that describe other restore operations that can be performed with Plug‑in for Oracle.

•
Renaming or relocating files
•
Duplicating a database in a non-RAC environment
•
Performing table-level recovery

Renaming or relocating files

With the RMAN backup method, the plug-in lets you rename the Control File and datafiles during restore. Renaming files can be useful if you do not want to overwrite the existing version and want to create a copy of the file. You can also relocate the files to a different directory while restoring it with the plug-in.

1
Complete the steps outlined in Preparing the database for recovery.
2
In the Navigation pane, click Create Restore Job, select Plug‑in for Oracle from the Plugin Type list.
3
In the saveset table, select the applicable item, and click Next.
For more information, see Selecting data for a restore.
4
On the Create Selection Set page, select the datafile or Control File to restore.
5
From the Actions list, select Rename.
6
In the Rename/Relocate dialog box, enter the applicable information.
•
Rename: Enter the new name.
•
Relocate: Enter the new path.
The plug-in uses the set newname RMAN command to restore or rename — or both — RMAN backups. The set newname command has precedence over the DB_CREATE_FILE_DEST parameter. If the full path is not specified for a restore or rename, the plug-in behaves as follows:
•
SPFILE: The file is restored to the “$ORACLE_HOME/dbs” directory with the new name.
•
Datafile:
•
If you specify a new location when the file is created, the file is restored or renamed to this location with the new name.
•
If you do not specify a new location when the file is created, the file is restored or renamed to “$ORACLE_HOME/dbs” with the new name.
 
* 
NOTE: A full path can include a path to an ASM location. For example: +DATA/my_db/my_datafile_renamed.dbf
When renaming the Control File during restore, the resulting filename should exist in the CONTROL_FILES list in the Oracle® Parameter File.
7
To apply changes, click OK.
The item is accompanied by the name and location information in parentheses.
8
Continue with the restore procedure as explained in Finalizing and submitting the job.

Duplicating a database in a non-RAC environment

A Duplicate Database backup lets you create a duplicate or clone of a source database for special purposes that does not affect the backup and restore procedures for the source database. RMAN supports duplicating databases to increase a DBA’s flexibility when performing the following tasks:

•
Testing backup and recovery procedures.
•
Testing an upgrade to a new release of Oracle® Database.
•
Testing the effect of applications on database performance.
•
Generating reports.

For more information on duplicating a multi-instance RAC database, see Duplicating a database in a RAC environment. For more information on Oracle’s Duplicate Database functionality, see Duplicating a Database in the Oracle Database Backup and Recovery User’s Guide.

The plug-in provides the following restore scenarios for the Duplicate Database backup:

•
Restoring a Duplicate Database to the same server
•
Restoring a Duplicate Database to an alternate server with the same directory structure
•
Restoring a Duplicate Database to an alternate server with an alternate directory structure
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating