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 : 20-07-2017
ORA-14132

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

  • ora-24184 : transformation string.string already exists
  • ora-24754 : cannot start new transaction with an active transaction
  • ora-13262 : geometry column string does not exist in table string
  • ora-30436 : unable to open named pipe 'string'
  • ora-07484 : snlkput: cannot convert(put) lock.
  • ora-27165 : tried to join thread that does not exist
  • ora-23483 : object "string"."string" not allowed in this operation.
  • ora-19683 : real and backup blocksize of file string are unequal
  • ora-30186 : '' must be followed by four hexdecimal characters or another ''
  • ora-24324 : service handle not initialized
  • ora-13144 : target table string not found
  • ora-29371 : pending area is not active
  • ora-29299 : Invalid handle for piecewise compress or uncompress
  • ora-32834 : Messaging Gateway agent user has not been set
  • ora-07594 : spiip: $GETJPIW failure
  • ora-19655 : cannot switch to incarnation with different resetlogs data
  • ora-26095 : unprocessed stream data exists
  • ora-24960 : the attribute string is greater than the maximum allowable length of number
  • ora-16657 : reinstatement of database in progress
  • ora-02184 : resource quotas are not allowed in REVOKE
  • ora-37141 : (XSSQLMDQ01) Invalid host variable syntax for MDQUERY procedure.
  • ora-23402 : refresh was aborted because of conflicts caused by deferred txns
  • ora-13188 : cell decode failed
  • ora-27048 : skgfifi: file header information is invalid
  • ora-14625 : subpartition contains rows corresponding to values being dropped
  • ora-38461 : XML Tag "string" already exists for the XMLType attribute "string"
  • ora-31641 : unable to create dump file "string"
  • ora-19810 : Cannot create temporary control file string in DB_RECOVERY_FILE_DEST
  • ora-08311 : sllfop: bad value for maxrecsize
  • ora-07512 : sscggtl: $enq unexpected return for client termination lock
  • 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.