Database Reference
In-Depth Information
Requirements of Transportable Tablespaces
Transportable tablespaces can be locally managed or dictionary managed and must meet
the following requirements:
In Oracle 9 i or higher, the transported tablespace does not have to be the same block
size as the target database's standard block size. However, the target database must
have a DB_nK_CACHE_SIZE initialization parameter set, where n is the block size of the
transportable tablespace.
The tablespace must be placed in read-only mode during the transport process.
Starting with Oracle 11 g , Oracle Data Pump is used instead of export/import to move
the metadata from the source to the target.
You can't import a transported tablespace that has the same name as an existing
tablespace in the target database. You can rename the transported tablespace as part
of the import process.
In order for an object to be transportable, all of the partitions that contain its depen-
dent objects such as indexes, materialized views, and partitioned tables must be
included in the tablespace set.
Tablespaces that do not use block encryption but have tables that have encrypted
columns are not transportable.
You can't transport the SYSTEM tablespace or objects owned by the SYS user.
Tablespaces with 8.0-compatible advanced queues with multiple recipients are not
transportable.
If you're transporting across platforms, RAW, BFILE, and AnyTypes are not converted
from one endian type to another as part of the transport process.
Step 1: Check Compatibility and Endian Format
If the source and target are different versions of the database, you'll need to verify the
minimum compatibility for transportable tablespaces. When you create a transportable
tablespace set, Oracle determines the minimum compatibility level for the target. Oracle
throws an error if the target database's compatibility level is lower than the minimum
compatibility. If you're transporting a tablespace to the same platform, the minimum
compatibility must be 8.0 for both the source and target. Both source and target must
have a minimum compatibility of 9.0 if the transportable tablespace's block size is differ-
ent than the target's standard block size. For different platforms, the minimum compat-
ibility must be 10.0 for both source and target.
Search WWH ::




Custom Search