NetVault Plug-in for Oracle 7.1 - User Guide

Recovery Type – Use these options to select the type of recovery to be performed.

Do Not Perform Recovery – Select this option if you want to restore the files but do not want to perform recovery.

Perform Complete Recovery – Select this option to recover an individual tablespace, multiple tablespaces, or the whole database to the most recent point in time, without the loss of any committed transactions.

Perform Tablespace Point in Time Recovery – Do not use this option. Tablespace Point-in-Time Recovery (TSPITR), which enables PIT Recovery on one or more tablespaces, is not currently supported.

Perform Table Level Point in Time Recovery – Select this option to recover specific tables to a particular point in time. Use a point-in-time control (System Change Number Based, Log Sequence Based, or Time Based) to specify the point in time to recover to, and use the Auxiliary Destination, Recover table, and Remap table controls to provide additional options for the recovery-table task. For more information and examples, see Performing table-level recovery.

Perform Database Point in Time Recovery – Select this option if you need to return a database to its state at a past point. For example, to reverse the effect of a user error, such as dropping a table, you might want to return the database to its contents before the deletion occurred.

Point-in-time controls – You can use one of the following options with the preceding options to specify a point in time to recover to.

System Change Number Based – For an SCN-based PIT Recovery, select this option, and specify the SCN until which the transactions must be recovered. RMAN will recover up to, but not including, the specified SCN.

Log Sequence Based – For a log-sequence-based PIT Recovery, select this option, and specify the terminating log sequence number and the thread to which it belongs. To identify the appropriate log sequence number and thread, you can query V$LOG_HISTORY to view the logs that have been archived.

Time Based – For a time-based PIT Recovery, select this option, and set the date and time in the fields provided. The plug-in will recover up to, but not including, the specified time.

Auxiliary Destination – Use this field to specify a directory (full path) that an Oracle-based automated auxiliary instance will use as part of the point-in-time recovery process. By default, this field lists a directory within the ORACLE_HOME directory. You can change this directory to any other location. This directory must exist before you execute the recovery process. For more information, see Performing table-level recovery.

Recover table – Enter a comma-separated list of tables that you want to include in a table-level recovery. For more information, see Performing table-level recovery.

Remap table – Enter a comma-separated list of tables that you want to rename as a part of a table-level recovery. For more information, see Performing table-level recovery.

Perform Trial Recovery Only – Only available for Oracle 10g and later, Enterprise Edition databases. Select this option to perform a Trial Recovery, which you can use to determine whether a recovery will succeed or encounter problems or whether a previous recovery has encountered a problem. It lets you look ahead into the redo stream to detect possible problems. The Trial Recovery applies redo in a way similar to normal recovery, but it does not write changes to disk and it rolls back its changes at the end of the Trial Recovery. If errors are encountered during the Trial Recovery, they are logged in the Oracle Alert Log as test run errors.

Recovery Options – These options pertain to the recovery phase.

Check Read-Only Datafiles and Recover if Not Current – Used in conjunction with the Check Read-Only Datafiles and Restore if Necessary Restore Option. Select this option to include read-only datafiles in the recovery process. The read-only files are included only if they are needed to complete recovery. If they are not damaged, RMAN will omit them.

Delete Restored Archive Logs No Longer Needed – The plug-in copies the archived redo logs to the directory from which they were backed up. Select this option to delete the restored archive logs that Oracle deems unnecessary.

Objects selected on the Create Selection Set page are ignored.

Mount Database Before Restore and Shutdown Abort Database First options on the Restore Options tab are honored.

Options selected on the Post Recovery tab are honored.

Perform Block Media Recovery – Select this option to perform Block Media Recovery and recover only the corrupted blocks versus recovering the entire datafile.

Recover All Corrupted Blocks – Select this option to recover all the corrupted blocks that are reported in V$DATABASE_BLOCK_CORRUPTION.

Specify Corrupted Blocks to Recover – When you only want to recover a certain subset of the corrupted blocks, select this option. In the corresponding text box, enter the datafile number and block number of each of the corrupted blocks that you want to recover. Enter one datafile-block entry per line in the following format:

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 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, archives any un-Archived Log files (including the current log), and discards any redo information that was not applied during recovery so that it will never be applied. This option must be selected in the following situations:

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 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 currently opened in Read Write mode by another 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.

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 user name specified in the preceding field.