Database Reference
In-Depth Information
9. Transport the tablespace set.
TSPITR uses transportable tablespaces to facilitate the movement of the tablespace data
files from the auxiliary database instance to the target database instance. To perform this
action, RMAN will first export needed metadata from the auxiliary database instance.
It will then shut down the auxiliary database instance. On the target system, RMAN
SWITCH commands are executed to cause the data file locations in the target database
control file to be switched to the newly recovered data files. Finally, the backed-up meta-
data will be restored to the target database so the data in the restored tablespaces will be
accessible to the target database.
10. Complete the operation.
The auxiliary database files will be removed after the operation is completed. The
target database tablespaces will be offline. You should back up those tablespaces, and
then you will need to bring those tablespaces online manually. Once you do, you will
find that the tablespaces contain the data in the version it existed in at the restore time
indicated in the RECOVER command.
TSPITR does not restore the point-in-time statistics for the objects contained in the
restored tablespaces. Thus, you should analyze the objects in the tablespaces after
completing the TSPITR.
Checking the Transport Set
When you perform a TSPITR, you want a transport set that is self-contained. This means
that the tablespaces in the transport set do not have external object references; that is,
they don't refer to objects that are not in the transport set. For example, suppose you are
transporting the USERS tablespace, and a table in that tablespace has an index in the INDEX
tablespace. In this case, you will not be able to transport the USERS tablespace unless
you also transport the INDEX tablespace. When you transport both the USERS and INDEX
tablespaces, you are transporting a wholly self-contained transport set.
RMAN will determine if the transport set is fully self-contained, but you may want to
check beforehand to save some time. You can query the TS_PITR_CHECK view. In our example,
USERS and INDEX_TBS are self-contained. If USERS is not transported with INDEX_TBS , then the
TSPITR will error out. To determine if USERS and INDEX_TBS are self-contained, you would
issue this query:
SQL> SELECT ts1_name, ts2_name, reason
2 FROM SYS.TS_PITR_CHECK
3 WHERE (
4 TS1_NAME IN ('USERS','INDEX_TBS')
5 AND TS2_NAME NOT IN ('USERS','INDEX_TBS')
6 )
7 OR (
8 TS1_NAME NOT IN ('USERS','INDEX_TBS')
Search WWH ::




Custom Search