Transport set violations when exporting tablespace with subpartitions
(Doc ID 469900.1)
Last updated on FEBRUARY 18, 2019
Applies to:Oracle Database - Enterprise Edition - Version 10.1.0.2 to 10.2.0.4 [Release 10.1 to 10.2]
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Information in this document applies to any platform.
Transportable tablespace feature is frequently used to move a single partition from one database to another. In order to transport a tablespace, tablespace must be self contained. In the other words, the tablespace to be exported must contain all or none of the partitions of a partitioned tables.
When partition is not composite, it is enough to exchange the partitions to a new tablespace and export the self-contained tablespace with transport_tablespace=yes option. Have a look at <Note 90585.1> for exporting tablespace with non-composite partitions.
This article with an example discusses the problems when exporting composite partitions. If transport set check finds violations, this is either reported as ORA-29341 during export or violations are reported in transport_set_violations view if transport set is verified with TRANSPORT_SET_CHECK.
This article with an example discusses the problems when exporting composite partitions created with or without subpartition templates.
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
|1- Exchanging a single partition of a composite partitioned table violates transportable set.|
|2- Using subpartition templates violates transportable set when exporting a tablespace with a composite partition.|