NetVault Plug-in for Oracle 13.0

Install the NetVault Client on an alternate node in the RAC environment. During the installation process, be sure to use the same NetVault Machine Name that was used during the installation of the NetVault Client on the original node. For example, if PROD_RAC was the NetVault Machine Name specified during the installation on the original node, PROD_RAC should be used as the NetVault Machine Name on the alternate node.

Install Plug‑in for Oracle.

After the NetVault Client has been installed on the selected node of the RAC environment, install the plug-in. The process is identical to installing the plug-in for a single-instance, non-RAC environment except that plug-in is installed on the NetVault Client that corresponds with the generic or virtual name provided as the NetVault Machine Name during the NetVault Client installation.


	IMPORTANT: If the relocation of the plug-in is expected to be permanent or last longer than 45 days, visit https://support.quest.com/contact-us/licensing and request relocation of the RAC Database-Based Plug‑in for Oracle license files.

With the plug-in installed on the alternate node, update the Oracle SID field on the Edit Oracle Database dialog box.

Enter the local SID for the target RAC database. The local SID is the instance name for the target RAC database on the node where the plug-in has been relocated. For more information, see Editing database information.

For more information on selecting data for backup, setting backup options, and finalizing and submitting the job, see Performing RMAN backups.

Restoring data in a RAC environment

Because RMAN is RAC-aware, it restores the selected data accordingly. With Plug‑in for Oracle installed on one of the nodes that hosts one of the instances for the RAC-enabled database, all RMAN-based restores are performed from this single installation of the plug-in. The restore process is similar to restoring single-instance, non-RAC environments, with the following exceptions:

•

During the Selecting data for a restore phase of performing RMAN restores, you might select a backup set from a node where the Oracle SID equals the Oracle SID of the instance on which the plug-in is running. But you might also select a backup set from an Oracle SID of a different RAC node for which backups were performed previously. For more information about performing restores after a node failure, see Performing restores after node failure.

•

During the Setting restore options phase, if authentication for the target database is needed, set the Target Database Authentication Details to the applicable values for the local Oracle instance on which the plug-in that is performing the restore resides. For more information, see Setting Destination Details.

For more information on preparing the database for recovery, selecting data items for a restore, setting restore options, finalizing and submitting the job, and opening the database for use, see Performing RMAN restores.


	IMPORTANT: If the plug-in was relocated to an alternate node and backups were performed from multiple instances, use the current Oracle SID when selecting data on the Create Selection Set page.

The following topics outline additional types of RMAN recovery that are available in a RAC environment.

•

Recovering a Whole Database to the same RAC environment

•

Restoring SPFILE in a RAC environment

•

Restoring Control Files in a RAC environment

•

Performing disaster recovery in a RAC environment

•

Performing restores after node failure

•

Duplicating a database in a RAC environment

Recovering a Whole Database to the same RAC environment

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 in a RAC environment.

From a terminal window, connect as the Oracle Software Owner to the node where Plug‑in for Oracle is installed.

Set the ORACLE_SID environment variable to the local instance.

export ORACLE_SID = <local_SID>

Start SQL*Plus, and connect with administrator privileges to the local instance.

SQLPLUS SYS AS SYSDBA

Shut down the local instance.

SHUTDOWN ABORT;

Start the local instance with the NOMOUNT option.

STARTUP FORCE NOMOUNT;

Disable the CLUSTER_DATABASE initialization parameter for the local instance.

ALTER SYSTEM SET CLUSTER_DATABASE=FALSE SCOPE=SPFILE SID='<local_SID>';

Shut down the local instance.

SHUTDOWN ABORT;

Exit SQL*Plus.

Shut down all RAC instances.

> srvctl STOP DATABASE -d <database_name> -o abort

Ensure that all RAC instances are shut down.

>srvctl STATUS DATABASE -d <database_name>

Start SQL*Plus, and connect with administrator privileges to the local instance.

SQLPLUS SYS AS SYSDBA

In SQL*Plus, start the local instance with the MOUNT option.

STARTUP MOUNT;

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

On the Create Selection Set page, select the Whole Database node, and click

Click the Restore Options tab, and select the applicable options:

•

To include read-only datafiles in the restore and recovery process, select Check Read-Only Datafiles and Restore if Necessary and 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 the Delete Archive Logs No Longer Needed option.

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 Database Point-in-Time Recovery: Recovers the database to a specific point whether it be a specific time, log sequence number, or SCN.

On the Recovery Catalog tab, select the Use Catalog option, and specify the Recovery Catalog connection details.

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 restores and recovers the database.

From a terminal window, connect as the Oracle Software Owner to the node where Plug‑in for Oracle is installed.

Start SQL*Plus, and connect with administrator privileges to the local instance.

SQLPLUS SYS AS SYSDBA

Enable the CLUSTER_DATABASE initialization parameter for the local instance.

ALTER SYSTEM SET CLUSTER_DATABASE=TRUE SCOPE=SPFILE SID='<local_SID>';

Shut down the local instance.

SHUTDOWN ABORT;

Exit SQL*Plus.

Start all RAC instances.

>srvctl START DATABASE -d <database_name>

Start all RAC Services.

>srvctl START SERVICE -d <database_name>

Ensure that all RAC instances are running.

>srvctl STATUS DATABASE -d <database_name>


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