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. |
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 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 |
19 |
From a terminal window, connect as the Oracle Software Owner to the node where Plug‑in for Oracle is installed. |
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, Quest recommends that you perform a Full or Incremental Level 0 backup with the entire database selected on the NetVault Backup Selections page. |
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. |
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. |
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. |
IMPORTANT: After restoring a Control File from an Autobackup, Quest recommends that you perform a Full or Incremental Level 0 backup with the entire database selected on the NetVault Backup Selections page. |
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.
© ALL RIGHTS RESERVED. 이용 약관 개인정보 보호정책 Cookie Preference Center