Databases Reference
In-Depth Information
4.
Import the tablespace set into the target database by running the Data Pump import
script generated by the
transport tablespace
command. You can perform the import by
using the Data Pump Import utility from the command line, but it's a whole lot simpler to
use the import script prepared for you by RMAN during the creation of the transportable
tablespace set, with the default name
impscrpt.sql.
SQL> @impscrpt.sql
Directory created.
Directory created.
PL/SQL procedure successfully completed.
Directory dropped.
Directory dropped.
SQL>
5.
Use the DBA_TABLESPACES view to check that the tablespace test2 has been imported to
the target database.
How It Works
In this recipe, we showed you how to transport tablespaces to the same operating system platform using RMAN
backups. The next recipe, Recipe 15-13, shows how to do this on different platforms.
This recipe shows how you can create transportable tablespace sets from RMAN backups. You must have a prior
backup of all the data files that belong to the transportable tablespace set and the archived redo logs, so RMAN can
use them to recover to the target point in time.
You can also transport tablespaces from a “live” database using an alternative transport tablespace technique
explained in the Oracle documentation (specifically, the Administrator's Guide). However, the big disadvantage in
using that method is that the transportable tablespaces must be put into read-only mode, thus affecting database
availability. It not only may be time-consuming to put the tablespaces into read-only mode, but users can't write
to those tablespaces during the tablespace transport. You don't have any of these limitations when you use RMAN
backups as the basis of your transportable tablespace operation.
You may use this capability of RMAN for creating transportable tablespace sets for reporting purposes.
Transportable tablespace sets are also highly useful during the instantiation of Oracle Streams. The one big
requirement for using RMAN backups to create transportable tablespaces is that your RMAN backups must be
recoverable to the SCN at which you want the transportable tablespaces to be.
RMAN first creates an auxiliary database instance through which it creates the transportable tablespace sets.
RMAN does quite a few things to prepare the transportable table set. Here's a summary of the actions set off when you
execute the
transport tablespace
command:
1.
RMAN checks to make sure that the tablespaces you want to transport are self-contained.
To be considered self-contained, the tablespace set you want to transport mustn't contain
references pointing outside those tablespaces, such as an index on a table that doesn't
belong to one of the tablespaces you're transporting. RMAN automatically executes
the
transport_set_check
procedure of the DBMS_TTS package at the beginning of the
tablespace transport process, to verify whether the tablespaces are self-contained, as
shown here:
Running TRANSPORT_SET_CHECK on recovery set tablespaces
TRANSPORT_SET_CHECK completed successfully
