You can transport a tablespace or a set of tablespaces between databases.
The following list of tasks summarizes the process of transporting a tablespace. Details for each task are provided in the subsequent example.
- Pick a self-contained set of tablespaces.
- At the source database, configure the set of tablespaces in read-only mode and generate a transportable tablespace set.
A transportable tablespace set (or transportable set) consists of data files for the set of tablespaces being transported and an export dump file containing structural information (metadata) for the set of tablespaces. You use Data Pump to perform the export.
- Transport the export dump file.
Copy the export dump file to a place that is accessible to the target database.
- Transport the tablespace set.
Copy the data files to a directory that is accessible to the target database.
If the source platform and target platform are different, then check the endian format of each platform by running the query on the
If the source platform's endian format is different from the target platform's endian format, then use one of the following methods to convert the data files:
PUT_FILEprocedure in the
DBMS_FILE_TRANSFERpackage to transfer the data files. These procedures convert the data files to the target platform's endian format automatically.
Use the RMAN
CONVERTcommand to convert the data files to the target platform's endian format.
Conversion of data files between different endian formats is not supported for data files having undo segments.
- (Optional) Restore tablespaces to read/write mode on the source database.
- At the target database, import the tablespace set.
Run the Data Pump utility to import the metadata for the tablespace set.
Example 5-1 Example
These tasks for transporting a tablespace are illustrated more fully in the example that follows, where it is assumed the following data files and tablespaces exist: