立即与支持人员聊天
与支持团队交流

NetVault Plug-in for Oracle 7.1 - 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-inin a failover cluster environment Using the plug-in with Oracle Data Guard Troubleshooting Glossary About Dell

Table-level requirements and limitations

To use automated table-level recovery, the directory specified in the “Auxiliary Destination” clause must exist prior to executing recovery. You can use an existing empty directory, or create a new directory, provided that the directory exists before starting the process.
You must use the CONFIGURE command to configure the channels in RMAN. The auxiliary database will use 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 will be populated in a Linux/UNIX directory, /oracle/nvbu_pitr_auxiliary_destination, which you created before executing 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 will be recovered with the same name as the original.)
By default, RMAN imports the recovered tables or table partitions into the target database. Prior to 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 in time, 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, if required, manually import the dump file into the target database instance using the Oracle Data Pump Import utility.

Performing table-level recovery from the NetVault Backup WebUI

In addition to the steps outlined in Performing RMAN restores, the following options apply specifically to table-level recovery.
1
In the Recovery Type section on the Perform Recovery tab, select the Perform Table Level Point in Time Recovery option.
2
Select the System Change Number Based, Log Sequence Based, or Time Based option.
If you select the System Change Number Based option, the plug-in instructs RMAN to use the “until scn” clause during table recovery. For example: until scn 5555638
If you select the Log Sequence Based option, the plug-in instructs RMAN to use the “until sequence <number> thread <number>” clause during table recovery. For example: until sequence 38 thread 1
If you select the Time Based option, the plug-in instructs RMAN to use the “until time” clause during table recovery. For example: until time "to_date('2013/11/23 06:59:00', 'yyyy/mm/dd hh24:mi:ss')"
3
In the Auxiliary Destination field, specify a directory (full path) that the auxiliary instances will use to store all the files needed, including copies of the controlfile, archived logs, and datafiles.
Use of this field is equivalent to the “auxiliary destination '<directoryFullPath>'” clause.
4
In the Recover table field, enter a comma-separated list of tables that you want to include in the recovery table as part of a table-level recovery.
Use the oracle_user_name.table_name construct. Be aware that Oracle 12c includes common users and local users, and that the naming convention used for the local users is similar to the Oracle Database user names in earlier versions of Oracle.
*IMPORTANT: When listing a table from a common user, use double quotation marks. While SQL*Plus accepts queries on the tables using a string that includes C## or c# and excludes the double quotation marks, RMAN does not.
Example 1: The following lists three tables for the sales user.
Example 2: The following example lists two tables for the common C##SALES user.
Use of the preceding example is equivalent to the recover table "C##SALES"."NORTHSALES", "C##SALES"."SOUTHSALES" clause.
5
In the Remap table field, enter a comma-separated list of tables that you want to rename, if applicable, as a part of a table-level recovery.
This option lets you recover the table and analyze it for appropriateness to determine whether to overwrite the original table. You do not need to provide a mapping for every table listed in the Recover table field; you only need to list the mapping for those tables that you want to rename temporarily.
Example 1: The following maps the sales.northsales table to sales.northsales_recovered.
Example 2: The following maps the sales.northsales table to sales.northsales_recovered.
Example 3: The following maps the sales.northsales table to sales.northsales_recovered.
Use of the preceding example is equivalent to the remap table "C##SALES"."NORTHSALES":"NORTHSALES_RECOVERED" clause.
相关文档

The document was helpful.

选择评级

I easily found the information I needed.

选择评级