• |
Same version of Oracle database software: The version and edition of Oracle for the destination database must be identical to the version and edition of Oracle being used for the source database. This requirement includes identical patch levels. |
• |
Duplicate Database backup available: A Duplicate Database backup must be completed successfully and made available. |
• |
Source database in open state: The source database must remain in an OPEN READ WRITE state during the entire Duplicate Database restore process. |
• |
Auxiliary instance prepared: RMAN’s backup-based Duplicate Database process requires the preparation of an auxiliary instance: |
1 |
Oracle password file for auxiliary instance created: Required if you want to use a password file versus OS authentication for the auxiliary connection when duplicating to the same host as the source database. For more information on creating a password file, see Creating and Maintaining a Password File in the Oracle Database Administrator’s Guide. |
2 |
Oracle Net connectivity established to auxiliary instance: The auxiliary instance must be available through Oracle Net by adding the instance to the “tnsnames.ora” file of both the source server and the alternate server. Additionally, on Windows platforms, perform the following command to start the instance: |
3 |
Auxiliary instance destination directories exist: The following destination directories for the auxiliary instance must be created on the server where the destination database resides. If the destination database stores its datafiles in ASM, the ASM instance name for the destination database must exist. |
4 |
PFILE created for auxiliary instance: A client-side PFILE for the Auxiliary Database must be created from the SPFILE of the source database. |
• |
Start SQL*Plus, and connect with administrator privileges to the source database. |
5 |
PFILE updated with auxiliary values: The PFILE created for the auxiliary instance must be updated with the parameter values specific to the auxiliary instance. |
• |
• |
Update the *.db_name= entry to reflect the name of the destination database. |
6 |
Auxiliary instance started in NOMOUNT state: The auxiliary instance must be started in NOMOUNT state with the PFILE that has been updated with the parameter values specific to the auxiliary instance. |
• |
Start SQL*Plus, and connect with administrator privileges to the auxiliary instance. |
• |
Start the instance in NOMOUNT state. |
8 |
Exit SQL*Plus. |
• |
NetVault software and the Plug‑in for Oracle installed: The same version of NetVault software and the plug-in must be installed and configured on the alternate server where the destination database resides. |
• |
NetVault: Specify the name of the NetVault Server where the source database server was added as a NetVault Client. |
• |
Do Restore From NetVault Server: Specify the name of the NetVault Server where the source database server was added as a NetVault Client. |
• |
Restore Backup taken from NetVault Client: Specify the NetVault Machine Name for the source database server. |
• |
Source Database Added to Plug‑in for Oracle Installed on Alternate Server: The source database must be added to the plug-in that is installed on the alternate (standby) server where the destination database resides. |
1 |
On the Create Restore Job — Choose Saveset page, find the applicable Duplicate Database backup, and click Next. |
2 |
On the Create Selection Set page, navigate to the source NetVault Client and database, select the Whole Database node, and click . |
3 |
4 |
In the Destination Database section: |
• |
Specify the Oracle Net Service name of the auxiliary instance in the Target Service field. |
• |
Specify the Oracle Home for the auxiliary instance. |
• |
Specify the Oracle SYSDBA User Name that is used by the plug-in to connect to the auxiliary instance. |
• |
Specify the Oracle SYSDBA Password. |
• |
Select the Use nofilenamecheck option. |
5 |
In the Duplicate From Database section: |
• |
Specify the Oracle SID for the source database. |
• |
Specify the Oracle Home for the source database. |
• |
Specify the Oracle SYSDBA User Name that is used by the plug-in to connect to the source database. |
• |
Specify the Oracle SYSDBA Password. |
6 |
In the Target Client list, select the NetVault Machine Name of the alternate server where the destination database resides. |
7 |
Continue with the restore procedure, including completion of the Schedule and Advanced Options lists. |
The following topics provide information for performing a table-level recovery:
• |
A table for which the FLASHBACK TABLE command is unavailable; for example, the Flashback Table cannot rewind because of structural changes, or the target point is older than the undo point. |
• |
To use automated table-level recovery, the directory specified in the “Auxiliary Destination” clause must exist before running recovery. You can use an existing empty directory, or create a directory, if the directory exists before starting the process. |
• |
You must use the CONFIGURE command to configure the channels in RMAN. The auxiliary database uses the same channels as the target database. |
• |
You cannot use the “REMAP” clause to recover tables with named NOT NULL constraints. |
© ALL RIGHTS RESERVED. Terms of Use Privacy Cookie Preference Center