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 : 28-06-2017
ORA-14291

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-01165 : MAXDATAFILES may not exceed string
  • ora-21521 : exceeded maximum number of connections in OCI (object mode only)
  • ora-32607 : invalid ITERATE value in MODEL clause
  • ora-02234 : changes to this table are already logged
  • ora-07619 : $IDTOASC failed translating an integrity level
  • ora-31426 : cannot modify active subscriptions
  • ora-38776 : cannot begin flashback generation - flash recovery area is disabled
  • ora-12461 : undefined level string for policy string
  • ora-29324 : SET COMPATIBILITY release string format is wrong
  • ora-16723 : setting AlternateLocation property conflicts with the redo transport setting
  • ora-07232 : slemcc: fclose error.
  • ora-12019 : master table is a synonym to a remote object
  • ora-08313 : sllfop: could not allocate buffers
  • ora-13352 : the coordinates do not describe a circle
  • ora-01606 : gc_files_to_locks not identical to that of another mounted instance
  • ora-14623 : Value string does not exist in subpartition string
  • ora-06577 : output parameter not a bind variable
  • ora-30360 : REF not supported with query rewrite
  • ora-38731 : Expected version string does not match string in log header.
  • ora-30965 : fragment does not fit into the VARCHAR2 VALUE column
  • ora-10926 : trace name context forever
  • ora-37006 : (AWLISTALL04) number writers
  • ora-28000 : the account is locked
  • ora-31046 : Incorrect argument(s) specified in the operator
  • ora-38727 : FLASHBACK DATABASE requires a current control file.
  • ora-02150 : invalid new tablespace name
  • ora-26518 : push queue synchronization error detected
  • ora-16157 : media recovery not allowed following successful FINISH recovery
  • ora-19268 : XQ0048 - namespace string does not match target namespace string
  • ora-32820 : subscriber queue and exception queue must use same message system link
  • 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.