Database Reference
In-Depth Information
the entire database and then roll it forward in its entirety. You would then need to export
the objects (or use transportable tablespaces) and import them into the database you were
trying to recover.
Of course, if you had a Data Pump logical backup of the database, and it was taken at the
point in time when you needed to restore the database to, then you could use that option.
There are several problems with this choice though, including the fact that it is not possible
to roll the data backed up in the Data Pump export forward in time after it's restored. Thus,
if your export was taken at 4 p.m. three days ago, then that is the image of the data that
you're going to see when you restore the export file to the database.
Oracle Database 12 c and RMAN now make it much easier to restore a given table or
table partition (singular or plural). Now you can use the RMAN RECOVER TABLE command
to indicate to RMAN what table (or tables) you wish to restore.
In this section, we will discuss the following:
Things to check before trying to restore and recover database tables and partitions
Restrictions when restoring and recovering database tables and partitions
Options to consider when performing table or table partition restores
An example of using RMAN to restore and recover a database table
Things to Check Before Trying to Restore and
Recover Database Tables and Partitions
Individual table and table partition restores are done using the RMAN interface. As with
everything else, there are some prerequisites that need to be met, including the following:
The database must have been in ARCHIVELOG mode when it was backed up.
After the backup, the database must have remained in ARCHIVELOG mode until the
point that you want to restore the database to.
You will need all the archived redo logs generated from the point in time when the
database backup started and the point in time to which you wish to restore the table
or partition.
For partition recovery, the COMPATIBLE parameter must be set to 11.1.0 or later.
A complete RMAN backup of the SYSTEM , SYSAUX , UNDO , and SYSEXT tablespaces must
be available (full backup or a base and subsequent incrementals).
You must have a backup of the tablespace(s) that contain the objects that you want
to restore. All of these backups must have been completed before the point in time to
which you want to restore the objects.
All tablespaces in the restore set must be restored to the same point in time.
The database you are restoring to (the target database) must be open in read-write mode.
The target database must be in ARCHIVELOG mode.
As with any point-in-time recovery, you will need to know the time, log sequence number,
or SCN that you want to restore the table or partitions to. If you've met these prerequisites,
Search WWH ::




Custom Search