Restoring the Control File should only be performed in the following cases:
1 |
From a terminal window, connect as the Oracle Software Owner to the node where Plug‑in for Oracle is installed. |
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. |
12 |
Start the local instance with the FORCE NOMOUNT option. |
15 |
Open the database with the RESETLOGS option. |
16 |
17 |
Start SQL*Plus, and connect with administrator privileges to the local instance. |
18 |
Enable the CLUSTER_DATABASE initialization parameter for the local instance. |
20 |
Exit SQL*Plus. |
If your goal is to create a copy of your target database for ongoing use on a standby RAC environment or independent RAC environment, do not use these procedures. Instead, use the Duplicate Database backup type, which is designed for this purpose. For more information, see Duplicating a database in a RAC environment.
For variations on the following disaster recovery procedure, see Performing Disaster Recovery in the Oracle Database Backup and Recovery Advanced User’s Guide.
To perform a disaster recovery without a Recovery Catalog, the following requirements must be met:
• |
Oracle RAC environment in place: You must have a properly configured Oracle RAC environment that matches the configuration as specified Performing User Managed backups. In addition, the same version of the Oracle database software must be installed in the RAC environment as it existed on the damaged RAC environment. The ORACLE_HOME should be identical on both the original and new node. You do not have to create the database, but you do need to configure Oracle Net Services and ASM for shared storage. |
• |
NetVault software and the Plug‑in for Oracle installed: The same version of NetVault software and the plug-in must be installed on one of the nodes in the RAC using the same NetVault Machine Name as previously defined for the RAC environment. Ensure that the plug-in default attributes are defined as specified in Configuring default attributes. |
• |
DBID of the source database identified: Identify the DBID of the damaged database. If the DBID was not recorded as part of the initial plug-in installation, you can obtain the DBID by examining the NetVault binary logs for RMAN-based backups of the source database. The DBID is also available on the Details dialog box or the Backup Contents tab. |
• |
Default Location for SPFILE must exist: The default location in the ASM shared storage must exist before performing the following steps. Failure to ensure that the default location exists results in an ORA-17502 Failed to create file error during the SPFILE restore. Additionally, the SPFILE location should be detailed in the PFILE with the SPFILE parameter. |
• |
Backups of all tablespaces made available: Verify that you have the latest backups of all the tablespaces. |
3 |
Start the local instance with the FORCE NOMOUNT option. |
5 |
Start the local instance with the FORCE NOMOUNT option. |
9 |
On the Create Restore Job — Choose Saveset page, find the latest available backup that included all the tablespaces, and click Restore. |
10 |
On the Create Selection Set page, navigate to the source NetVault Client and database, select the Whole Database node, and click . |
11 |
Click the Restore Options tab, and select the Check Read-Only Datafiles and Restore if Necessary and Check Read-Only Datafiles and Recover if Not Current options to include read-only datafiles in the restore and recovery process. |
12 |
Because recovery must be performed in a disaster recovery scenario, on the Perform Recovery tab, select Perform Database Point-in-Time Recovery. |
13 |
14 |
17 |
© ALL RIGHTS RESERVED. Feedback Conditions d’utilisation Confidentialité Cookie Preference Center