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%.
When it is not feasible to
consolidate the database resources, database systems tend to grow in
different geographical locations and in different departments and
often in different operating systems or platforms. In such cases,
the feature of Oracle Transportable Tablespace offers an efficient
way of sharing large subsets of data and then sharing the processing
on this data on different hardware resources. This also is a key
requirement for effective grid-enabling architecture.
Transportable Tablespace gives
the grid users a very fast and efficient mechanism to move large
data from one database system to another. Another feature that is
particularly useful for large enterprises is the facility of
mounting read-only tablespace by two or more databases.
With 10g release, it becomes
possible to move the transportable tablespace across different
platforms or operating systems. Another new feature is the provision
of big tablespaces, which support ultra-large tablespaces to store
A transportable tablespace
allows the quick movements of a subset of an Oracle database from
one Oracle database to another. However, in the previous
release of Oracle server, it was only possible to move a tablespace
across Oracle databases within the same platform. Oracle 10g is
going one step further by allowing the movement of tablespace across
different platforms. This feature becomes particularly significant
in the Grid framework where many different operating systems coexist
and conduct data movements and data sharing.
The limitation requiring
transportable tablespaces to be transferred to the same operating
system has been removed. However, to transport tablespaces across
different platforms, both the source and target databases must be at
least on Oracle Database 10g, be on at least version 10.0.1, and
have the compatible initialization parameter set to 10.0. Using the
new cross-platform transportable tablespace method to move data is
more efficient than the traditional method of export and import.
Oracle Database 10g supports
many platforms for transportable tablespace. A new data dictionary
view, v$transportable_platform, lists all the supported platforms,
along with platform ID and endian format.
The v$database data dictionary
view also adds two columns, platform ID and platform name:
name, platform_id,platform_name from v$database;
2 Solaris[tm] OE (64-bit)
For example, it is not necessary
to convert the data file to transport a tablespace from an AIX-based
platform to a Sun platform, since both platforms use a big endian.
However, to transport a tablespace from a Sun Platform (big endian)
to a Linux Platform (little endian), the CONVERT command in the RMAN
utility should be used to convert the byte ordering. This can
be done on either the source platform or the target platform.