1 |
3 |
Execute the following command, where <database_name> represents the database that is being added to the plug-in: |
• |
Oracle SID – 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 is installed. |
• |
Parameter File(s) Path – In a multi-instance RAC environment, the plug-in requires the usage of an SPFILE as a dynamic means of maintaining initialization parameters. The SPFILE must be stored on the shared storage in ASM. Because the SPFILE is included in the Control File Autobackups, this field should be left blank in a RAC environment. |
• |
Control File Autobackup enabled – Select this option because Control File Autobackups are required in a RAC environment. |
IMPORTANT: If the relocation of the plug-in is expected to be permanent or last longer than 45 days, visit https://support.quest.com/licensing-assistance to request a relocation of the RAC Database-Based Plug‑in for Oracle license keys. |
3 |
With the plug-in installed on the alternate node, update the Oracle SID field on the Edit Oracle Database dialog. |
• |
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 another 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, you must 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. |
2 |
Set the ORACLE_SID environment variable to the local instance. |
3 |
Start SQL*Plus, and connect with administrator privileges to the local instance. |
5 |
Start the local instance with the NOMOUNT option. |
6 |
Disable the CLUSTER_DATABASE initialization parameter for the local instance. |
8 |
Exit SQL*Plus. |
11 |
Start SQL*Plus, and connect with administrator privileges to the local instance. |
12 |
13 |
On the Create Restore Job - Choose Saveset page, find the latest available backup that included all the tablespaces, and click Next. |
14 |
15 |
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. |
16 |
• |
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-in-time whether it be a specific time, log sequence number, or SCN. |
17 |
On the Recovery Catalog tab, select the Use Catalog option, and specify the Recovery Catalog connection details. |
18 |
20 |
Start SQL*Plus, and connect with administrator privileges to the local instance. |
21 |
Enable the CLUSTER_DATABASE initialization parameter for the local instance. |
23 |
Exit SQL*Plus. |
IMPORTANT: After completing a restore of the Whole Database, Dell strongly recommends that you perform a Full or Incremental Level 0 backup with the entire database selected on the NetVault Backup Selections page. |
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. 使用条款 隐私 Cookie Preference Center