My Oracle Support Banner

Transportable Tablespace (TTS) Restrictions and Limitations: Details, Reference, and Version Where Applicable (Doc ID 1454872.1)

Last updated on MARCH 30, 2020

Applies to:

Oracle Database Backup Service - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
Oracle Database Cloud Schema Service - Version N/A and later
Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Information in this document applies to any platform.

Purpose

This article has been written to draw together the restrictions that apply to the TRANSPORTABLE TABLESPACE Feature.


These restrictions consist of standard documented restrictions and areas where certain database features do not
transport and have been raised as Oracle Bugs.

Each restriction will be detailed with Documentation references and Versions given, where applicable. Example links to the 11.2 and 12.1 documentation may be referenced.

NOTE: In the images and/or the document content below, the user information and data used represents fictitious data from the Oracle sample schema(s) or Public Documentation delivered with an Oracle database product. Any similarity to actual persons, living or dead, is purely coincidental and not intended in any manner.

 

Scope

This Document is to be available for those using the Oracle Transportable Tablepsace Feature.

To use this Document please click on one of the details above which will guide you to the point required.

Details

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Purpose
Scope
Details
 Default DATA_PUMP_DIR does not work with PDBs
 When using the IMPDP utility, and the option TRANSPORT_TABLESPACES
 When using the IMPDP utility, the TRANSPORT_DATAFILES parameter
 When using the IMPDP utility, and the option TRANSPORT_FULL_CHECK
 When using the IMPDP utility, and the option TRANSPORTABLE
 When using EXPDP utility, and the option TRANSPORT_TABLESPACES
 Index Organized Tables (IOT) can become corrupt when using Transportable Tablespace
 It is not possible to transport the SYSTEM, SYSAUX, TEMP tablespaces or objects owned by the user SYS
 Transportable Tablespace import using IMPDP fails when the tablespace contains a spatial index
 Jobs performed in transportable tablespace mode have specific requirements to prevent the EXPDP/IMPDP job from failing
 Exporting a Schema In an 11.2 Database With a 10g Client Gives ORA-1455
 Considerations for Time Zone File Versions in Transportable Tablespace Mode
 Character Set and National Character Set Limitation
 Tablespace with the same name already exists
 Objects with Underlying Objects - Materialized Views or Partitioned Tables
 Objects where owner on destination is new
 Size Limitations
 Tablespace containing spatial indexes
 Tablespace containing XML Types
 Using Advanced Queues in Transportable tablespaces
 Opaque Types (such as RAW, BFILE, and the AnyTypes) can be transported, however.
 Floating-Point Numbers BINARY_FLOAT and BINARY_DOUBLE types
 Traditional EXP/IMP with 11.2 is desupported
 Traditional EXP/IMP Restrictions with Oracle 9i
 Encrypted tablespaces have the following limitations
 Database Charactersets Compatibility between Source and Destination
 Compatibility Considerations for Transportable Tablespaces
 OLAP Application AW Transportability
References

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.