If you want
to customize RMAN TSPITR, you can use
an RMAN-managed auxiliary instance and
make the following changes:
•
Rename
the recovery set data files using SET NEWNAME so that they are not restored and
recovered in their original locations.
•
Control
the location of your auxiliary set data files by specifying new names for
individual files with SET NEWNAME and using DB_FILE_NAME_CONVERT to provide
rules for converting data file names in the target database to data file names
for the auxiliary database.
•
Use
existing image copies of the recovery set and auxiliary set data files on disk
rather than restoring them from backup for faster RMAN TSPITR performance.
Oracle
recommends that you allow RMAN to manage the creation and destruction of the
auxiliary instance used during RMAN TSPITR. However, creating and using your
own auxiliary instance is supported.
•
To
create an Oracle instance suitable for use as an auxiliary instance, perform
the following steps:
•
1. Create an Oracle password file for the
auxiliary instance by using the orapwd utility.
•
2. Create a text initialization parameter file
for the auxiliary instance.
•
3. Verify Oracle Net connectivity to the
auxiliary instance using a valid net service name.
To perform
TSPITR, complete the following steps:
•
4. Start the auxiliary instance in NOMOUNT mode.
•
5. Connect the RMAN client to target and
auxiliary instances.
•
6. Execute the RECOVER TABLESPACE command.
Troubleshooting
RMAN TSPITR
File name
conflicts: If your use of SET NEWNAME, CONFIGURE AUXNAME, and
DB_FILE_NAME_CONVERT cause multiple files in the auxiliary or recovery sets to
have the same name, you receive an error during TSPITR. To correct the problem,
specify different values for these parameters to eliminate the duplicate name.
Insufficient
sort space during Export: When RMAN exports the metadata about recovered
objects from the auxiliary instance, it uses space in the temporary tablespace
for sorting. If there is insufficient space in the temporary tablespace for the
sorting operation, you need to increase the amount of sort space available.
Edit the recover.bsq file, found in $ORACLE_HOME/rdbms/admin, to remove the
comment characters from the following lines in the file:
sql clone "create
tablespace aux_tspitr_tmp
datafile ''/tmp/aux_tspitr_tmp.dbf''
size 500K";
RMAN cannot
identify tablespaces with undo segments: During TSPITR, RMAN needs information
about which tablespaces had undo segments at the TSPITR target time. This
information is usually available in the recovery catalog, if one is used. If
there is no recovery catalog, or if the information is not found in the
recovery catalog, RMAN proceeds assuming that the set of tablespaces with undo
segments at the target time is the same as the set of tablespaces with undo
segments at the present time. If this assumption is not correct, the TSPITR
operation fails and an error is reported. To prevent this from happening,
provide a list of tablespaces with undo segments at the target time in the UNDO
TABLESPACE clause.
Restarting
manual auxiliary instance after TSPITR failure: If you are managing your own
auxiliary instance and there is a failure in TSPITR, then before you can retry
TSPITR, you must shut down the auxiliary instance, correct the problem, and put
the auxiliary instance back in NOMOUNT mode.
