The Clone Database tab is available only when an RMAN DUPL DB backup is selected on the Create Selection Set page. You can use it to specify the options for restoring a Duplicate Database backup to a destination database. For more information on the prerequisites, see Duplicating a database in a non-RAC environment or Duplicating a database in a RAC environment.
• |
Duplicate Database: Select this option to restore the selected Duplicate Database backup to an alternate destination database. |
• |
Destination Database section: |
• |
Auxiliary Instance: Specify the Oracle Net Service name of the auxiliary instance. This field defaults to auxdb. |
• |
Oracle Home: Specify the Oracle Home for the auxiliary instance. This field defaults to the Oracle Home of the source database. |
• |
Oracle SYSDBA User Name: Specify the SYSDBA user name that is used to connect to the auxiliary instance. This field defaults to the SYSDBA user name specified in the configuration of the source database. |
• |
Oracle SYSDBA Password: Enter the password for the SYSDBA user name specified in the preceding field. |
• |
Use nofilenamecheck Option: Select this option to prevent RMAN from verifying whether the datafiles and online redo logs files of the source database are in use when the source database files use the same names as the duplicate database files. You are responsible for determining that the duplicate operation does not overwrite useful data. |
• |
Duplicate From Database section: |
• |
Target Database: Specify the Oracle SID of the target database. This field defaults to the Oracle SID of the database including in the backup. |
• |
Oracle Home: Specify the Oracle Home for the source database. This field defaults to the Oracle Home of the source database. |
• |
Oracle SYSDBA User Name: Specify the SYSDBA user name that is used to connect to the source database. This field defaults to the SYSDBA user name specified in the configuration of the source database. |
• |
Oracle SYSDBA Password: Enter the password for the SYSDBA user name specified in the preceding field. |
Intended for the advanced DBA, the Generate RMAN Script feature lets you generate most of an RMAN script through the WebUI. Later, before using the script, you can add more options or parameters. With this option, you do not need to create the script from scratch, which minimizes the risk of syntax errors in the scripts and that restores are not performed correctly.
You can set the following options for the Generate RMAN Script feature:
• |
Output RMAN Script to File: Select this option to use the feature and enable access to the remaining options, and then enter the name of the file to which the RMAN script is written. |
• |
RMAN Script Directory: Enter the name of the directory where the RMAN scripts are saved. The Generate Script Default Directory field defaults to the directory specified on the plug-in’s Configure dialog box. However, you can modify the field on a per-backup-job basis. The full path where the RMAN script is saved is built by concatenating the RMAN Script Directory with the filename provided in the Output RMAN Script to File field. |
• |
If Existing, Overwrite Destination File: Select this option to allow the destination file where the RMAN script is output to be overwritten if the file exists. If the file exists and this option is not selected, Generate RMAN Script fails and does not write output to the existing file. Select this option only if you are sure that you want to overwrite an existing file. |
• |
Generate RMAN Script and Submit Job: With this option selected, in addition to outputting the RMAN script to the specified file, the NetVault Job is scheduled and submitted. Clearing this option ensures that the plug-in only generates the script, which lets you edit and run the script outside of NetVault. |
• |
Do not Include Connect Strings: To exclude connection strings from the file because they might include Oracle passwords, select this option. Selecting this option ensures that Oracle passwords are not included in the RMAN script file. |
Complete the steps outlined in Finalizing and submitting the job under Performing User Managed restores.
The following topics describe the types of recovery that you can perform in a non-RAC environment:
For information on the types of RMAN recoveries available in a RAC environment, see Restoring data in a RAC environment.
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Nutzungsbedingungen Datenschutz Cookie Preference Center