Chat now with support
Chat mit Support

NetVault Plug-in for Oracle 10.0.5 - User Guide

Introducing Dell™ 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 Troubleshooting Glossary

Uses of table-level recovery

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).
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.
You cannot use the “REMAP” clause to recover tables with named NOT NULL constraints.

Configuring channels for table-level recovery

RMAN> CONFIGURE CHANNEL <channelNumber> DEVICE TYPE sbt

Performing table-level recovery from the RMAN CLI

Table-level recovery requires the use of the “until” clause to define the state that you want to recover to.
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.
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.)
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.
Verwandte Dokumente

The document was helpful.

Bewertung auswählen

I easily found the information I needed.

Bewertung auswählen