Chat now with support
Chat mit Support

NetVault Plug-in for Oracle 12.2 - User Guide

Introducing Quest® NetVault® Backup Plug-in  for Oracle Defining a backup strategy Installing and removing the plug-in Configuring the plug-in Backing up data Using the Oracle Flashback Database Restoring data
Restoring and recovering data: an overview Performing User Managed restores Using advanced User Managed restore procedures Performing RMAN restores Using RMAN types of recovery in a non-RAC environment Using advanced procedures with RMAN restores
Maintaining the Recovery Catalog Using the RMAN CLI Using the Plug-in with Oracle RAC Using the Plug-in in a failover cluster environment Using the plug-in with Oracle Data Guard Using the plug-in with Oracle Container Databases (CDBs) and Pluggable Databases (PDBs) Troubleshooting

Setting Post Recovery options

When performing recovery using the Whole Database, All Tablespace, or Disaster Recovery options, the database is in a MOUNT state during the restore and recovery process. You must return the database to the OPEN state after completion. The plug-in provides the flexibility of opening the database automatically after the recovery process during the restore.

The Post Recovery tab includes the following options:

•
Open Database after Recovery: Select this option to open the database automatically and make it available for normal use after the recovery process is completed during the restore. Selecting this option makes the following options available:
•
Read Write: Opens the database in read/write mode, which lets you generate redo logs. This option is the default if you are opening a primary database.
•
Read Write and Reset Logs: Opens the database in read/write mode and resets the current log sequence number to 1. It also archives any un-Archived Log files, including the current log, and discards any redo information that was not applied during recovery so that it is never applied. This option must be selected in the following situations:
•
After performing incomplete media recovery or media recovery using a backup Control File.
•
After a previous OPEN RESETLOGS operation did not complete.
•
After a FLASHBACK DATABASE operation.
•
Read Only: Select this option to restrict users to read-only transactions, which prevents them from generating redo logs. This option is the default setting when you open a physical standby database, so that the physical standby database is available for queries even while archive logs are being copied from the primary database site. Oracle has the following restrictions on opening a database with the Read Only option:
•
You cannot open a database in Read Only mode if it is opened in Read Write mode by a different instance.
•
You cannot open a database in Read Only mode if it requires recovery.
•
You cannot take tablespaces offline while the database is open in Read Only mode. However, you can take datafiles offline and online, and you can recover offline datafiles and tablespaces while the database is open in Read Only mode.

Setting Destination Details

If the SYSDBA user name or password or the Oracle SID for the database has changed since the time of backup, set the following options for the restore job on the Destination Details tab:

•
Target Service: This option is required only if the current SID for the Oracle DBID has been changed since the backup was taken.
•
Oracle SYSDBA User Name: Specify the new SYSDBA user name if changed.
•
Oracle SYSDBA Password: Specify the password associated with the name specified in the preceding field.
 
* 
IMPORTANT: The Destination Details requires that the DBID of the backed-up or source database match the DBID of the destination database. When the goal of the restore is to create a duplicate of the source database to a database with a different DBID, using a Duplicate Database backup is required. For more information, see Duplicate Database backup.

Setting the Recovery Catalog details

While the Recovery Catalog information is provided for backups on the Configure or Add, or Edit, Oracle Database dialog box, set the Recovery Catalog configuration for a particular restore job by configuring the Recovery Catalog information on the Recovery Catalog tab.

•
Use Catalog: Select this option to use the RMAN repository in the Recovery Catalog and store information about this restore operation in a Recovery Catalog. Clear Use Catalog when performing a test recovery.
The following fields are enabled when you select this option:
•
Catalog Instance Name: Enter the Oracle Instance name, which might differ from the Oracle Net Service name, for the Recovery Catalog database. This instance name must be defined in the “tnsnames.ora” file on the Oracle Database Server so that the plug-in can connect to the Recovery Catalog database. If the Recovery Catalog was used during the backup, the Instance Name field defaults to the Oracle Instance name used during the backup job.
•
Catalog Owner: Specify the user that was specified as the owner of the Recovery Catalog and was granted the RECOVERY_CATALOG_OWNER role.
•
Catalog Password: Provide the password associated with the Catalog Owner name specified in the preceding field.

Setting the Clone Database options

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.
This option is required when you restore a duplicate database to an alternate server. Do not select this option if you are restoring a duplicate database to the same server; otherwise, the restore job fails with the following errors:
•
RMAN-10035: exception raised in RPC: ORA-19504: failed to create file
•
ORA-27086: skgfglk: unable to lock file – already in use
•
SVR4 Error: 11: Resource temporarily unavailable
•
RMAN-10031: ORA-19624 occurred during call to DBMS_BACKUP_RESTORE. RESTOREBACKUPPIECE
•
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.
Verwandte Dokumente

The document was helpful.

Bewertung auswählen

I easily found the information I needed.

Bewertung auswählen