NetVault Plug-in for Oracle 7.1

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.

•

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

•

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.

Configuring channels for table-level recovery

To use the plug-in for recovery, you must 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:

RMAN> SHOW ALL;

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

RMAN> CONFIGURE DEFAULT DEVICE TYPE TO 'SBT_TAPE';

When these settings are added for SBT channels and a table-level recovery is executed, at least one DISK channel and one SBT channel will be available for the recovery process. Note that the auxiliary instance will use the same channels that are available for the target instance.

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

RMAN> CONFIGURE CHANNEL <channelNumber> DEVICE TYPE sbt

For more information on configuring channels, refer to 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, refer to your Oracle documentation. Note the following:

•

Table-level recovery requires the use of the “until” clause to define the state that you want to recover to.

•

The following examples assume that you are connected to the target instance and, if applicable, the RMAN recovery catalog.

Examples

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.

RMAN> recover table SALES.NORTHSALES, SALES.SOUTHSALES, SALES.CENTRALSALES

until scn 5555638

auxiliary destination '/oracle/nvbu_pitr_auxiliary_destination';

RMAN> recover table SALES.NORTHSALES, SALES.SOUTHSALES, SALES.CENTRALSALES

until sequence 38 thread 1

auxiliary destination '/oracle/nvbu_pitr_auxiliary_destination';

RMAN> recover table SALES.NORTHSALES, SALES.SOUTHSALES, SALES.CENTRALSALES

until time "to_date('2013/11/23 06:59:00', 'yyyy/mm/dd hh24:mi:ss')"

auxiliary destination 'C:\app\Administrator\product\11.2.0\dbhome_1\nvbu_pitr_auxiliary_destination';

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.)

RMAN> recover table SALES.NORTHSALES, SALES.SOUTHSALES, SALES.CENTRALSALES

until time "to_date('2013/11/23 06:59:00', 'yyyy/mm/dd hh24:mi:ss')"

remap table sales.northsales:northsales_recovered, sales.southsales:southsales_recovered

auxiliary destination 'C:\app\Administrator\product\11.2.0\dbhome_1\nvbu_pitr_auxiliary_destination';

Recovers a table from a common user:

RMAN> recover table "C##SALES"."NORTHSALES", "C##SALES"."SOUTHSALES"

until scn 5555638

remap table "C##SALES"."NORTHSALES":"NORTHSALES_RECOVERED"

auxiliary destination '/oracle/nvbu_pitr_auxiliary_destination';

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.

RMAN> recover table "C##SALES"."NORTHSALES", "C##SALES"."SOUTHSALES"

until time 'SYSDATE-4'

auxiliary destination '/oracle/nvbu_pitr_auxiliary_destination'

datapump destination '/oracle/nvbu_pitr_datapump_destination'

dump file 'northsales_southsales_export_dump.dat'

notableimport;


	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.

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.

In the Recovery Type section on the Perform Recovery tab, select the Perform Table Level Point in Time Recovery option.

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')"

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.


	IMPORTANT: This directory must exist before you execute the recovery process. If the directory does not exist, recovery might fail with an ORA-type error.

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.

For containers where common users are in place, Oracle Database supplies the SYS and SYSTEM common users. The name of user-created common users must begin with C## or c#. For more information, refer to the Oracle 12c Multitenant Architecture documentation.


	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.

sales.northsales, sales.southsales, sales.centralsales

Example 2: The following example lists two tables for the common C##SALES user.

"C##SALES"."NORTHSALES", "C##SALES"."SOUTHSALES"

Use of the preceding example is equivalent to the recover table "C##SALES"."NORTHSALES", "C##SALES"."SOUTHSALES" clause.

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.

sales.northsales:northsales_recovered

Example 2: The following maps the sales.northsales table to sales.northsales_recovered.

sales.northsales:northsales_recovered, sales.southsales:southsales_recovered

Example 3: The following maps the sales.northsales table to sales.northsales_recovered.

"C##SALES"."NORTHSALES":"NORTHSALES_RECOVERED"

Use of the preceding example is equivalent to the remap table "C##SALES"."NORTHSALES":"NORTHSALES_RECOVERED" clause.

Documentos relacionados

The document was helpful.

Selecione a classificação

I easily found the information I needed.

Selecione a classificação

Selecione seu produto:

Para podermos atendê-lo melhor, informe o Propósito de seu chat:

Soluções recomendadas para seu problema

NetVault Plug-in for Oracle 7.1 - User Guide

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