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

NetVault Plug-in for Oracle 11.3 - User Guide

Introducing Quest® 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

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 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. Oracle® 12c includes common users and local users, and 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.

Maintaining the Recovery Catalog

Resynchronizing the Recovery Catalog

Plug‑in for Oracle automatically runs a full or partial resynchronization of the Recovery Catalog when performing RMAN backups as long the Control File is mounted and the Recovery Catalog database is available at command execution.

You can use RMAN’s RESYNC CATALOG command to perform manual Full Resynchronizations when:

You should not need to run RESYNC CATALOG often. For more information, see Using CROSSCHECK to Update the RMAN Repository in the Oracle® Database Backup and Recovery Advanced User’s Guide.

To force a Full Resynchronization of the Recovery Catalog, perform the following steps.

> rman TARGET / CATALOG rman/<password>@<connect_identifier for catalog>

Using CROSSCHECK to update the RMAN repository

To ensure that data about backups in the RMAN Repository is synchronized with corresponding data in the NetVault Database, perform a crosscheck. The CROSSCHECK command updates outdated RMAN repository information about backups whose repository records do not match their physical status. For example, if a user removes archive logs from disk with an OS command, the repository still indicates that the logs are on disk, when in fact they are not.

For more information on the CROSSCHECK command, see the Oracle® Database Backup and Recovery Basics guide.

> rman TARGET / CATALOG rman/<password>@<connect_identifier for catalog>
相关文档

The document was helpful.

选择评级

I easily found the information I needed.

选择评级