- Movement between different character sets
- Movement between different OS (depending on RDBMS version)
- Some objects are not transferred via TTS. 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.
- Oracle Server -- Standard Edition vs. Enterprise Edition; Standard Edition can only import TTS (no export)
- System, undo, sysaux and temporary tablespaces cannot be transported.
Transporting tablespaces with XMLTypes has the following limitations:
-
The destination database must have XML DB installed.
-
Schemas referenced by XMLType tables cannot be the XML DB standard schemas.
-
Schemas referenced by XMLType tables cannot have cyclic dependencies.
-
XMLType tables with row level security are not supported, because they cannot be exported or imported.
-
If the schema for a transported XMLType table is not present in the
destination database, it is imported and registered. If the schema
already exists in the destination database, an error is returned unless
the
ignore=y
option is set.
-
If an XMLType table uses a schema that is dependent on another
schema, the schema that is depended on is not exported. The import
succeeds only if that schema is already in the destination database.
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.
Comments