ORA-14130: UNIQUE constraints mismatch in ALTER TABLE EXCHANGE PARTITION

Cause : One of the tables named in the ALTER TABLE EXCHANGE PARTITION command has a UNIQUE constraint for which no matching (vis-a-vis key columns) constraint is defined on the other table or a matching constraint is defined on the other table, but it differs from that defined on the first table vis-a-vis being enabled and/or validated.

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

Ensure that for every UNIQUE constraint defined on one of the tables named in the ALTER TABLE EXCHANGE PARTITION statement there is a matching (vis-a-vis key columns and being enabled and/or validated) UNIQUE constraint defined on the other table. If UNIQUE constrains are enabled, UNIQUE constraints on the partitioned table should be enforced using local indexes.

update : 30-04-2017

ORA-14130 - UNIQUE constraints mismatch in ALTER TABLE EXCHANGE PARTITION
ORA-14130 - UNIQUE constraints mismatch in ALTER TABLE EXCHANGE PARTITION

  • ora-02256 : number of referencing columns must match referenced columns
  • ora-31464 : target table for the change table no longer exists
  • ora-13850 : Tracing for client identifier string is not enabled
  • ora-01196 : file string is inconsistent due to a failed media recovery session
  • ora-38736 : Wrong thread number string in flashback log file header.
  • ora-39959 : invalid warning number (string)
  • ora-30484 : missing window specification for this function
  • ora-02792 : Unable to fstat() a file being used for asynchronous I/O.
  • ora-00821 : Specified value of sga_target stringM is too small, needs to be at least stringM
  • ora-06001 : NETASY: port set-up failure
  • ora-09854 : snyPortInfo: bad return code from request.
  • ora-00102 : network protocol string cannot be used by dispatchers
  • ora-03296 : cannot resize datafile - file string not found
  • ora-16701 : generic resource guard request failed
  • ora-13019 : coordinates out of bounds
  • ora-22915 : cannot ALTER a nested table's storage table to ADD/MODIFY columns
  • ora-26502 : error resignal
  • ora-00393 : log string of thread string is needed for recovery of offline datafiles
  • ora-19663 : cannot apply current offline range to datafile string
  • ora-08467 : error converting Oracle number to string
  • ora-12715 : invalid character set specified
  • ora-13188 : cell decode failed
  • ora-22957 : NULL is an invalid input to powermultiset and COLLECT functions
  • ora-30454 : summary contains STDDEV without corresponding SUM & COUNT
  • ora-32128 : setDataBuffer called after fetch has started
  • ora-38759 : Database must be mounted by only one instance and not open.
  • ora-29807 : specified operator does not exist
  • ora-30068 : Internal Event to turn on nested
  • ora-24172 : rule set string.string has errors
  • ora-02185 : a token other than WORK follows COMMIT
  • 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.