Transportable Tablespaces and Databases
There are different solutions to satisfy the need to transport
the data between databases in Oracle. Data Pump can be used to
export logical backup of the database and import it to another
database or database links can be used to copy the objects between
databases. But these basic methods are more time consuming than a
more advanced way, particularly if dealing with terabytes of data.
Transportable Tablespace (TTS) Feature
The advanced way to do this is by using the Transportable
Tablespace (TTS)feature of
RMAN. Using this feature, the datafiles which contain actual data
can be copied, thus making the migration faster. This feature was
firstly introduced in Oracle 8i which allowed copying the data
between databases that used the same block size faster than a
In version 9i, Oracle introduced a multiple block size feature,
and so removed that restriction from TTS. In Oracle 10g Release 1,
the Cross Platform transportable tablespace
feature was introduced that allows the moving of datafiles between
platforms that use different endian formats. In Oracle 10g Release
2, a transportable database feature was introduced which allows
transporting the whole database to the different platform with the
same endian format.
This chapter will explain and demonstrate in practical terms the
following TTS methods:
Transporting tablespaces between two
databases with the same platform using both RMAN backups and live
Transporting a single tablespace
between two databases running on the different platforms
(Cross-Platform transportable tablespace)
Transporting the whole database to the
different platform (Cross-Platform transportable database)
The first scenario will be divided into two parts: in the first
part, the tablespace will be transported using RMAN backup, while in
the second part, no backup will be used and tablespaces will be
copied from the running database instance. In the second scenario, a
cross-platform transportation of the tablespace from Solaris OS to
Linux will be performed. In the third scenario, the whole database
that runs on Windows OS will be transported to the Linux OS.
Transportable Tablespace can be used to:
Transport the tablespace from the test
environment to the production database
Transport data from a production
database to a data warehouse system
Publish data to customers
Perform Tablespace Point in Time
Upgrade the database to the new
The following are the limitations of the Transporting Tablespace
It is not
possible to transport the system tablespace and the objects that
are owned by the user SYS.
must be running with a compatible
parameter set to 10.0 or higher.
In Oracle 10g,
the tablespace must be set to read/write so it can be transported
to another platform. However this restriction is
not available in Oracle 11g. The
tablespace does NOT have to be put in read/write mode before
transporting it to another platform in Oracle 11g.
set and national character set must be the same for both source
and target databases.
cannot be transported that is already present in the target
database until and unless either the source tablespace or target
tablespace is renamed before the tablespace transport.
Burleson is the American Team
documentation was created as a support and Oracle training reference for use by our
DBA performance tuning consulting professionals.
Feel free to ask questions on our
considering using the services of an Oracle support expert should
independently investigate their credentials and experience, and not rely on
advertisements and self-proclaimed expertise. All legitimate Oracle experts
Oracle technology is changing and we
strive to update our BC Oracle support information. If you find an error
or have a suggestion for improving our content, we would appreciate your
and include the URL for the page.
Copyright © 1996 - 2020
All rights reserved by
is the registered trademark of Oracle Corporation.