This is an excerpt from the bestselling book
Oracle Grid & Real Application Clusters. To get immediate
access to the code depot of working RAC scripts, buy it
directly from the publisher and save more than 30%.
To transport a tablespace from
one platform to another, datafiles on different platforms must be in
the same endian format, byte ordering. The pattern for byte ordering
in native types is called endianness. There are only two main
patterns, big endian and little endian. Big endian means the
most significant byte comes first, and little endian means the least
significant byte comes first. If the source platform and the target
platform are of different endianness, an additional step must be
taken on either the source or target platform to convert the
tablespace being transported to the target format. If they are
of the same endianness, no conversion is necessary and tablespaces
can be transported as if they were on the same platform.
However, there are certain
restrictions in using the transportable tablespace:
* The source and target database
must use the same character set and national character set.
* A tablespace cannot be
transported to a target database in which a tablespace with the same
name already exists. However, the tablespace to be transported or
the destination tablespace can be renamed before the transport
operation. Renaming a tablespace is a new feature in 10g.
* The set should be
between Databases: A General Procedure
Perform the following steps to
move or copy a set of tablespaces.
1. Pick a self-contained set of
tablespaces. Verify this using the dbms_tts.transport_set_check
2. Next, generate a
transportable tablespace set, using the Export utility.
3. A transportable tablespace
set consists of the set of datafiles for the set of tablespaces
being transported and an Export file containing metadata information
for the set of tablespace and corresponding data files.
4. Transporting a tablespace set
to a platform different from the source platform will require
connection to the Recovery Manager (RMAN) and invoking the CONVERT
command. An alternative is to do the conversion on the target
platform after the tablespace datafiles have been transported.
5. Next, the tablespace datafile
set is transported. Copy the datafiles and the export file
containing the metadata to the target database. This can be
accomplished using any facility for copying flat files, such as the
operating system copy utility, ftp, or publishing on CDs or DVDs.
6. The final step is to plug in
the tablespace. Use the Import utility to plug the set of
tablespaces metadata, and hence the tablespaces themselves, into the
7. If these tablespaces are
being transported to a different platform, the Recovery Manager
CONVERT command can be used to perform the conversion.
Note: As an alternative to
conversion before transport, the CONVERT command can be used for the
conversion on the target platform after the tablespace set has been