ORA-14291: cannot EXCHANGE a composite partition with a non-partitioned table

Cause : A ocmpsoit epatritoin acn nolyb e xechnage dwiht ap arittinoedt abel.

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

Enusret ha tth etalbe ebin gexhcanegd si pratiitonde o rthta taht hte aprttiio nbenig xechnage disn onc-omopsiet.

update : 21-08-2017

ORA-14291 - cannot EXCHANGE a composite partition with a non-partitioned table
ORA-14291 - cannot EXCHANGE a composite partition with a non-partitioned table

  • ora-07579 : spini: $DCLEXH failure
  • ora-23502 : valid directory for offline instatiation is not specified
  • ora-14129 : INCLUDING INDEXES must be specified as tables have enabled UNIQUE constraints
  • ora-12982 : cannot drop column from a nested table
  • ora-36964 : (XSRELTBL09) workspace object is not a valid level relation.
  • ora-19999 : skip_row procedure was called
  • ora-23378 : connection qualifier "string" is not valid for object group "string"."string"
  • ora-02208 : duplicate MAXTRANS option specification
  • ora-24061 : cannot specify non-zero SECONDARY_INSTANCE if PRIMARY_INSTANCE was zero
  • ora-19116 : too many xmlspace declarations
  • ora-10388 : parallel query server interrupt (failure)
  • ora-40219 : apply result table string is incompatible with current operation
  • ora-16590 : Data Guard configuration does not contain a primary database
  • ora-39201 : Dump files are not supported for estimate only jobs.
  • ora-22275 : invalid LOB locator specified
  • ora-13154 : invalid precision specified
  • ora-25279 : dequeue as select not supported before 8.2
  • ora-13499 : %s
  • ora-22285 : non-existent directory or file for string operation
  • ora-06924 : CMX: wrong break message length
  • ora-01122 : database file string failed verification check
  • ora-30966 : error detected in the XML Index layer
  • ora-09826 : SCLIN: cannot initialize atomic latch.
  • ora-16029 : cannot change LOG_ARCHIVE_MIN_SUCCEED_DEST, no archive log destinations
  • ora-25149 : Columns of UROWID type may not be indexed
  • ora-25506 : resource manager has not been continuously on in some instances
  • ora-36276 : (XSCGMDLAGG06) The current operator does not need a weight variable.
  • ora-22994 : source offset is beyond the end of the source LOB
  • ora-39067 : Unable to close the log file.
  • ora-24050 : subscribers are not supported for exception queue string
  • 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.