2 |
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 to request relocation of the RAC Database-Based Plug‑in for Oracle license keys. |
With Plug‑in for Oracle installed on the alternate node, the restore process is similar to performing restores in a single-instance, non-RAC environment except for the following differences:
• |
During the Selecting data for a restore phase of performing RMAN restores, select the backup set from the node on the Create Selection Set page where the Oracle SID equals the Oracle SID of the instance where the plug-in was originally installed before the relocation. |
• |
During the Setting restore options phase, set the Target Database Authentication Details to the appropriate values for the local instance on the alternate node where the plug-in now 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.
PFILE updated with auxiliary values: In addition to the updates to the PFILE as specified in the Non-RAC duplication procedures, the following additional updates must be made when the source database is a multi-instance database:
1 |
• |
<database/instance_name>.cluster_database=TRUE |
• |
<instance_name>.instance_number=N |
• |
<instance_name>.thread = N |
• |
After completion of the Restore Duplicate Database Procedure as defined in the Duplicating a database in a non-RAC environment, you can convert the resulting single-instance database to a multi-instance database. To do so, use one of the procedures detailed in Converting to Oracle Real application Clusters from Single-Instance Oracle Databases in the Oracle Real Application Clusters Installation Guide.
© ALL RIGHTS RESERVED. Terms of Use Privacy Cookie Preference Center