139 Which three statements must be true before transporting a tablespace from a database on one plat

139
Which three statements must be true before transporting a tablespace from a database on one platform to
a database on another platform? (Choose three.)
A. Both source and target database must be the same character set
B. Both source and target database must have the same endian format
C. The COMPATIBLE parameter must be the same in the source and target databases.
D. The minimum compatibility level for both the source and target database must be 10.0.0.
E. All read-only and offline data files that belong to the tablespace to be transported must be platform

aware.

Correct Answer: ABD
Section: (none)
Explanation

Explanation/Reference:

Explanation:
http://download.oracle.com/docs/cd/B28359_01/server.111/b28310/tspaces013.htm#ADMIN01101
Limitations on Transportable Tablespace Use
The source and target database must use the same character set and national character set.
You cannot transport a tablespace to a target database in which a tablespace with the same name already
exists. However, you can rename either the tablespace to be transported or the destination tablespace
before the transport operation.
Objects with underlying objects (such as materialized views) or contained objects (such as partitioned
tables) are not transportable unless all of the underlying or contained objects are in the tablespace set.

Encrypted tablespaces have the following the limitations:
Before transporting an encrypted tablespace, you must copy the Oracle wallet manually to the destination
database, unless the master encryption key is stored in a Hardware Security Module
(HSM) device instead of an Oracle wallet. When copying the wallet, the wallet password remains the same
in the destination database. However, it is recommended that you change the password
on the destination database so that each database has its own wallet password. See Oracle Database

Advanced Security Administrator’s Guide for information about HSM devices, about
determining the location of the Oracle wallet, and about changing the wallet password with Oracle Wallet
Manager.
You cannot transport an encrypted tablespace to a database that already has an Oracle wallet for
transparent data encryption. In this case, you must use Oracle Data Pump to export the tablespace’s
schema objects and then import them to the destination database. You can optionally take advantage of
Oracle Data Pump features that enable you to maintain encryption for the data while it is being
exported and imported.
See Oracle Database Utilities for more information.
You cannot transport an encrypted tablespace to a platform with different endianness.
Tablespaces that do not use block encryption but that contain tables with encrypted columns cannot be
transported. You must use Oracle Data Pump to export and import the tablespace’s schema objects. You
can take advantage of Oracle Data Pump features that enable you to maintain encryption for the data while
it is being exported and imported. See Oracle Database Utilities for more information.
Beginning with Oracle Database 10g Release 2, you can transport tablespaces that contain XMLTypes.
Beginning with Oracle Database 11g Release 1, you must use only Data Pump to export and import the
tablespace metadata for tablespaces that contain XMLTypes.
The following table shows the minimum compatibility requirements of the source and target tablespace in
various scenarios. The source and target database need not have the same compatibility setting.