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 : 22-09-2017

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

  • ora-09828 : SCLFR: atomic latch return error.
  • ora-22990 : LOB locators cannot span transactions
  • ora-01647 : tablespace 'string' is read only, cannot allocate space in it
  • ora-02755 : osnfsmcre: cannot create chared memory file ?/dbs/ftt_.dbf
  • ora-02073 : sequence numbers not supported in remote updates
  • ora-06595 : REF CURSOR parameters are not supported in forwarded RPC calls
  • ora-13524 : error encountered while retrieving baseline information
  • ora-07215 : slsget: getrusage error.
  • ora-09974 : skxfidini: Error Initializing SDI Channel
  • ora-08314 : sllfcf: Error closing file
  • ora-32130 : invalid offset/index refrenced in Bytes
  • ora-29860 : cannot truncate a table with domain indexes marked LOADING
  • ora-31093 : null or invalid value specified for parameter : string
  • ora-03254 : unable to execute the sql in read only database
  • ora-24007 : invalid value string, MAX_RETRIES should be non-negative integer
  • ora-01491 : CASCADE option not valid
  • ora-13266 : error inserting data into table string
  • ora-24389 : Invalid scrollable fetch parameters
  • ora-30568 : cannot drop log group - nonexistent log group
  • ora-28180 : multiple authentication methods provided by proxy
  • ora-10565 : Another test recovery session is active
  • ora-13857 : Invalid module name
  • ora-07282 : sksaprd: string overflow.
  • ora-29929 : missing SCAN Keyword
  • ora-09790 : sllfcf: unable to close file.
  • ora-04000 : the sum of PCTUSED and PCTFREE cannot exceed 100
  • ora-12007 : materialized view reuse parameters are inconsistent
  • ora-19729 : File string is not the initial version of the plugged in datafile
  • ora-19688 : control file autobackup format(string) for string does not have %F
  • ora-25156 : old style outer join (+) cannot be used with ANSI joins
  • 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.