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 Database software installed: Install the same version of the Oracle database software on the system as existed on the damaged server. The ORACLE_HOME should be identical on both the source and destination Oracle server. You do not have to create the database. |
• |
Oracle password file created: Use the orapwd utility to create the Oracle password file. |
• |
Oracle service on Windows created and started: Create the Oracle Service on Windows with Oracle’s oradim utility. The Oracle SID should be identical to the original or source database. This option creates an identical Oracle Service name. For example, from an OS prompt run: |
• |
NetVault Backup software and Plug‑in for Oracle installed: The same version of NetVault Backup software and the plug-in must be installed and configured as it originally existed on the damaged server. Ensure that the plug-in’s default attributes are defined as specified in Configuring default settings. |
• |
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 for Oracle installation, look for it in the NetVault Backup 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: Verify that the default location for the SPFILE exists. Failure to do so results in an ORA-17502 Failed to create file error during the SPFILE restore. |
• |
Backups of all tablespaces made available: Verify that you have the latest backups of all the tablespaces. |
To perform the recovery, complete the following steps.
6 |
Restore the SPFILE from Autobackup. |
IMPORTANT: If you do not have an Autobackup of the Control File, complete the steps in Retrieving a Control File manually before continuing. |
9 |
On the Create Restore Job — Choose Saveset page, find the latest available backup that included all the tablespaces, and click Next. |
10 |
On the Create Selection Set page, navigate to the source NetVault Backup Client and database, select the Whole Database node, and click Edit Plugin Options. |
11 |
Click the Restore Options tab, and select the applicable options: |
• |
To mount the database before the performing the restore, select Mount Database Before Restore. |
• |
To include read-only datafiles in the restore, select Check Read-Only Datafiles and Restore if Necessary. |
12 |
Because recovery must be performed in a disaster recovery scenario, on the Perform Recovery tab, select Perform Database Point-in-Time Recovery. |
13 |
On the Perform Recovery tab, select Check Read-Only Datafiles and Recover if Not Current to include read-only datafiles in the recovery process. |
14 |
On the Recovery Catalog tab, clear the Use Catalog option to ensure that the Recovery Catalog is not used for this restore. |
15 |
17 |
IMPORTANT: After completing a disaster recovery, Quest recommends that you perform a Full or Incremental Level 0 backup with the database selected on the Create Selection Set page. |
1 |
On the Create Restore Job — Choose Saveset page, find the latest available backup that is marked with “Controlfile Included.” |
3 |
Use the REPLICATE CONTROLFILE command to copy the restored Control File. |
This topic contains subtopics that describe other restore operations that can be performed with Plug‑in for Oracle.
2 |
In the Navigation pane, click Create Restore Job, select Plug‑in for Oracle from the Plugin Type list. |
4 |
On the Create Selection Set page, select the datafile or Control File to restore. |
5 |
6 |
In the Rename/Relocate dialog box, enter the applicable information. |
• |
Rename: Enter the new name. |
• |
Relocate: Enter the new path. |
• |
SPFILE: The file is restored to the “$ORACLE_HOME/dbs” directory with the new name. |
• |
NOTE: A full path can include a path to an ASM location. For example: +DATA/my_db/my_datafile_renamed.dbf |
7 |
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Términos de uso Privacidad Cookie Preference Center