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 : 26-04-2017
ORA-14132

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

  • ora-08101 : index key does not exist file string: (root string, node string) blocks (string)
  • ora-07760 : slemtr: $open failure
  • ora-22347 : No changes to type specified for ALTER TYPE
  • ora-09823 : device name is too long
  • ora-28053 : the account is inactive
  • ora-01679 : database must be mounted EXCLUSIVE and not open to activate
  • ora-10979 : trace flags for join index implementation
  • ora-00223 : convert file is invalid or incorrect version
  • ora-26683 : invalid value for value_type
  • ora-13868 : Instance-wide SQL tracing on instance string is not enabled
  • ora-36378 : (XSAGTHRWEIGHT) While running AGGREGATE with multiple threads, the weight variable workspace object specified by your ARGS variable workspace object must exist in the same analytic workspace as your AGGMAP workspace object.
  • ora-14101 : partition extended table name cannot refer to a synonym
  • ora-39764 : specified stream is not in the specified direct path context
  • ora-24124 : invalid ACTION parameter passed to DBMS_REPAIR.string procedure
  • ora-25470 : duplicate attribute value for variable: string
  • ora-02027 : multi-row UPDATE of LONG column is not supported
  • ora-09921 : Unable to get information label from connection
  • ora-23417 : unknown materialized view type: string
  • ora-33336 : (DSSEXIST04A) Analytic workspace string is not attached.
  • ora-02295 : found more than one enable/disable clause for constraint
  • ora-16801 : redo transport-related property is inconsistent with database setting
  • ora-02829 : No segment of the proper size is available
  • ora-22826 : cannot construct an instance of a non instantiable type
  • ora-12477 : greatest lower bound resulted in an invalid OS label
  • ora-08179 : concurrency check failed
  • ora-08432 : raw data has invalid floating point data
  • ora-40222 : data mining model export failed, job name=string, error=string
  • ora-06254 : NETNTT: cannot share connection to cube
  • ora-23327 : imported deferred rpc data does not match string of importing db
  • ora-27508 : IPC error sending a message
  • 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.