Databases Reference
In-Depth Information
Or when using Oracle Database 11g or lower, use this syntax:
RMAN> sql 'alter tablespace p_dt online';
RMAN> sql 'alter tablespace p_idx online';
■
if you are not using a recovery catalog, you can perform TSpiTr only once on a tablespace. you will be
allowed to perform another TSpiTr only from a backup taken after the first TSpiTr was performed. This is because after
performing TSpiTr, the control file has no record of the previous incarnation of the tablespace you recovered. Therefore,
you won't be able to recover this tablespace again from the backup taken before TSpiTr was performed. however, when
using a recovery catalog, you can “cry mulligan” and perform multiple TSpiTrs if you discover that you restored your
tablespace(s) to the wrong point. Therefore, we recommend you use a recovery catalog if you foresee the need to perform
multiple TSpiTrs on a tablespace.
Caution
RMAN performs many tedious tasks for you with automated TSPITR. Here are the steps that RMAN performs
for you:
1.
Creates an auxiliary instance, starts it, and connects to it
2.
Takes offline tablespaces that are involved with TSPITR
3.
Restores the backup control file that corresponds to the target restore time
4.
Restores data files to a destination specified by your AUXILIARY DESTINATION
5.
Recovers restored data files in an auxiliary location
6.
Opens an auxiliary database with the
resetlogs
command
7.
Exports the auxiliary data dictionary metadata about recovered tablespaces and shuts
down the auxiliary database
8.
Issues a
switch
command on the target database to update the control file to point at the
recovered auxiliary data files
9.
Imports objects associated with recovered tablespaces into the target database
10.
Deletes the auxiliary data files
After step 10 is complete, your target database should have the tablespaces recovered to the point listed in the
recover
command. The rest of the tablespaces in your database should be as they were before you initiated the
TSPITR. You need to back up any tablespaces involved in the TSPITR and then alter them online.
Many limitations are involved with TSPITR. Here are some situations where you cannot use TSPITR:
•
If the database is not running in archivelog mode or is missing required archive redo logs
•
Attempting to recover a tablespace that was renamed to a point in time before it was renamed;
you must use the prior name of the tablespace to perform TSPITR
•
If there are constraints on objects that refer to objects in other tablespaces, you must perform
TSPITR on all tablespaces involved
•
Cannot perform TSPITR on the default tablespace for your database
•
Cannot perform TSPITR on tablespaces that contain materialized views or partitioned tables
unless all of the associated objects are contained within the tablespaces being recovered
