My Oracle Support Banner

Common Causes of ORA-14097 At Exchange Partition Operation (Doc ID 1418545.1)

Last updated on APRIL 28, 2021

Applies to:

Oracle Database - Enterprise Edition - Version 8.1.7.0 and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
Information in this document applies to any platform.

Purpose

To provide information about various frequently experienced cases that can lead to ORA-14097.

Scope

Useful to DBA's or anyone who are working with partitioned tables e.g. doing partition exchange load.

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
 CASE 1:Partitioned and Non-Partitioned tables are not structurally identical
 CASE 2:Presence of UNUSED columns
 CASE 3:Presence of Function Based Indexes
 CASE 4: When trying to exchange any partitions of existing tables with a new table created using "CREATE TABLE AS SELECT" command from the original partition table an ora-14097 error is encountered
 CASE 5: ALTER TABLE EXCHANGE PARTITION fails even though both tables have the same column names and data types when a column has been added via alter table
 CASE 6: When trying to exchange any partitions of existing tables with a table from the original partition table an ora-14097 error is encountered. The VALIDATED status of the constraint on any of the table has status as "NOT VALIDATED"
References

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