This section lists the limitations on transportable tablespace.

Be aware of the following limitations for transportable tablespaces:

• The general limitations described in "General Limitations on Transporting Data" apply to transportable tablespaces.

• When transporting a tablespace set, 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.

• Transportable tablespaces cannot transport tables with TIMESTAMP WITH TIMEZONE (TSTZ) data across platforms with different time zone file versions. The transportable tablespace operation skips these tables. You can export and import these tables conventionally.

  See Oracle Database Utilities for more information.

• You cannot include administrative tablespaces, such as SYSTEM and SYSAUX in a transportable tablespace set.

• Transportable tablespaces cannot contain any tables with columns that are encrypted using TDE column encryption

• If a tablespace is encrypted using TDE, you can only transport this tablespace to a platform that uses the same endian format. If you need to go across endianness, you must decrypt, transport, and re-encrypt the tablespace. Starting with Oracle Database release 12.2 these operations can be performed online.

• Transportable tablespace sets include TDE policies only. Other security policies (such as redaction policies, masking policies, and so on) are not included and they must be recreated after the tablespace is imported into the new database.