NetVault Plug-in for Oracle 12.2


	IMPORTANT: The examples shown throughout the following topics are based on using the fully automated version of the auxiliary instance. By using the automated method, the auxiliary instance is fully created and managed by the Oracle Server whenever a destination, that is, a directory in the file system, is provided.

To restore tablespaces to the auxiliary instance, you must provide backups of the system tablespaces, the tablespaces that contain the tables to recover, and the controlfile as it existed at the time of the backup.

The plug-in lets you take advantage of the automated recovery method using an auxiliary instance. For information regarding other methods of performing table-level recovery, see your Oracle documentation. These other methods let you use the RMAN command prompt to recover from backups created by the plug-in.

The following topics provide information for performing a table-level recovery:

•

Uses of table-level recovery

•

Table-level requirements and limitations

•

Configuring channels for table-level recovery

•

Performing table-level recovery from the RMAN CLI

•

Performing table-level recovery from the NetVault Backup WebUI

Uses of table-level recovery

Table-level recovery lets you recover one or more tables or table partitions to a specific point without affecting other tables or database objects. You can use backups created using the plug-in's RMAN backup method to accomplish this process. In addition to other recovery methods, table-level recovery is useful when you need to recover:

•

A few tables to a specific point.

•

Tables that were dropped and purged.

•

Tables that are logically corrupted.

•

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.

Table-level requirements and limitations

There are Oracle Database-specific limitations and requirements for performing this type of recovery. To perform recovery successfully, review the following requirements and limitations. For more information, including a complete list of constraints, see the table-level recovery information in your Oracle documentation.

•

Table-level recovery is available in the Enterprise Edition of Oracle Server 12.1 or later.

•

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.

•

Full backups of the tablespaces SYSTEM, SYSAUX, undo, that is, UNDOTBS1, and SYSEXT, if the SYSEXT tablespace is present, must exist. The tablespace that contains the table that is the target of the recovery must also exist.

•

You cannot use table-level recovery to recover: tables that belong to SYS, tables from the SYSTEM and SYSAUX tablespaces, or tables on standby databases.

•

You cannot use the “REMAP” clause to recover tables with named NOT NULL constraints.