NetVault Plug-in for Oracle 11.3 - User Guide

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:

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.

Configuring channels for table-level recovery

To use the plug-in for recovery, configure SBT channels in RMAN. These channels connect RMAN and the NetVault Backup media management utilities. You can configure a default SBT channel, as well as additional channels of type SBT or DISK. To display the current RMAN configuration, run the following command from an RMAN prompt:

If no SBT channels are configured, that is, only settings for DISK channels exist, use the following command to instruct RMAN to add a set of settings for SBT channels:

When these settings are added for SBT channels and a table-level recovery is run, at least one DISK channel and one SBT channel are available for the recovery process. The auxiliary instance uses the same channels that are available for the target instance.

You can also use the following command to add additional channels, if applicable:

For more information on configuring channels, see your Oracle® documentation.

Performing table-level recovery from the RMAN CLI

As stated previously, the examples are based on using the fully automated version of the auxiliary instance. For additional examples on using an automated auxiliary instance or a user-managed auxiliary instance, both of which can be used with the plug-in to perform table-level recovery, see your Oracle® documentation. Note the following:

The following example recovers three tables of an Oracle® user, sales, to a specific SCN using a fully automated auxiliary instance for which the required files are populated in a Linux® or UNIX® directory, /oracle/nvbu_pitr_auxiliary_destination, which you created before running recovery.

Similar example except that it uses a log sequence:

Similar example except that it uses a specific date and time, and it is based on a Windows Server® environment:

Using the remap table option, the following example recovers two of the three selected tables to a new table with a different name. The third table is recovered with the same name as the original.

Recovers a table from a common user:

By default, RMAN imports the recovered tables or table partitions into the target database. Before import, the tables are stored in an export dump file. You can use the NOTABLEIMPORT option to prevent RMAN from importing the recovered tables or table partitions. If you use this option, the tables are recovered to the specified point, and the export dump file is created, but the dump file is not imported into the target database. At that point, you can analyze the tables using the auxiliary instance, or manually import the dump file into the target database instance using the Oracle Data Pump Import utility.

NOTE: If errors occur during recovery, Oracle does not delete the export dump file if the recovered table created one. You can then use the export dump file to complete the recovery process manually.