ORA-14132: table cannot be used in EXCHANGE

Cause : An attempt was made to issue an ALTER TABLE EXCHANGE PARTITION | SUBPARTITION command, but the non-partitioned table cannot be used in the EXCHANGE because one or more of the following apply: - it is a typed table - it contains ADT columns - it contains nested-table columns - it contains REF columns - it contains array columns - it is an index-organized table - it contains LOB columns - it is a nested table - it is created with row dependency and the partitioned table is not - it is created without row dependency and the partitioned table is

Action - How to fix it : DBA Scripts :: www.high-oracle.com/scripts

Make sure the non-partitioned table does not violate any of the above restrictions for the ALTER TABLE EXCHANGE PARTITION | SUBPARTITION command.

update : 28-05-2017
ORA-14132

ORA-14132 - table cannot be used in EXCHANGE
ORA-14132 - table cannot be used in EXCHANGE

  • ora-29520 : name string resolved to a class in schema string that could not be accessed
  • ora-12599 : TNS:cryptographic checksum mismatch
  • ora-19800 : Unable to initialize Oracle Managed Destination
  • ora-25020 : renaming system triggers is not allowed
  • ora-38607 : FI minimum and maximum itemset length not between [1, string]
  • ora-00253 : character limit string exceeded by archive destination string string
  • ora-06741 : TLI Driver: unable to open protocol device
  • ora-24460 : Native Net Internal Error
  • ora-27476 : "string.string" does not exist
  • ora-16648 : a new observer registered with identifier string
  • ora-40105 : input data incompatible with model signature
  • ora-01867 : the interval is invalid
  • ora-06960 : Failed to access log file
  • ora-25003 : cannot change NEW values for this column type in trigger
  • ora-01905 : STORAGE keyword expected
  • ora-24003 : Queue table index string inconsistent with queue table string
  • ora-01343 : LogMiner encountered corruption in the logstream
  • ora-28541 : Error in HS init file on line number.
  • ora-01607 : cannot add logfile to the specified instance
  • ora-29392 : cpu parameters for level string for plan string must be zero
  • ora-04002 : INCREMENT must be a non-zero integer
  • ora-14455 : attempt to create referential integrity constraint on temporary table
  • ora-06548 : no more rows needed
  • ora-29521 : referenced name string could not be found
  • ora-16777 : unable to find the destination entry of a standby database in V$ARCHIVE_DEST
  • ora-12689 : Server Authentication required, but not supported
  • ora-13511 : invalid INTERVAL string, must be in the range (string, string)
  • ora-07226 : rtneco: unable to get terminal mode.
  • ora-22053 : overflow error
  • ora-13711 : Some snapshots in the range [string, string] are missing key statistics.
  • Oracle Database Error Messages



    Oracle Database High Availability Any organization evaluating a database solution for enterprise data must also evaluate the High Availability (HA) capabilities of the database. Data is one of the most critical business assets of an organization. If this data is not available and/or not protected, companies may stand to lose millions of dollars in business downtime as well as negative publicity. Building a highly available data infrastructure is critical to the success of all organizations in today's fast moving economy.

    Well, the reason for above error is that i have taken the above script from a 11g database and running it on 10g database. 11g has bring some changes in password management. Below code is executed on 11g and user created successfully, which is expected result.