• |
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.
Similar example except that it uses a log sequence:
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.
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 |
• |
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, archive logs, and datafiles. |
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. |
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. |
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. |
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 the RMAN 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.
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Terms of Use Privacy Cookie Preference Center