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 : 17-08-2017
ORA-14130

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

  • ora-16568 : cannot set property string
  • ora-23395 : object "string"."string" of type "string" does not exist or is invalid
  • ora-30175 : invalid type given for an argument
  • ora-31528 : could not find change set string for CDC subscription string
  • ora-22852 : invalid PCTVERSION LOB storage option value
  • ora-12922 : concurrent ALTER DATABASE [NO] FORCE LOGGING command is running
  • ora-23496 : can not change disabled status for "string" and "string"
  • ora-02381 : cannot drop PUBLIC_DEFAULT profile
  • ora-06307 : IPA: Cannot reset connection
  • ora-24393 : invalid mode for creating connection pool
  • ora-16101 : a valid start SCN could not be found
  • ora-15035 : no disks belong to diskgroup "string"
  • ora-09243 : smsget: error attaching to SGA
  • ora-07613 : $GETJPIW failed in retrieving the user's process label
  • ora-25438 : invalid variable name: string
  • ora-12002 : there is no materialized view log on table "string"."string"
  • ora-00285 : TIME not given as a string constant
  • ora-02153 : invalid VALUES password string
  • ora-13240 : specified dimensionality greater than that of the query mbr
  • ora-31463 : logfile location string is an empty directory
  • ora-16813 : log apply service not running on apply instance string recorded by the broker
  • ora-32050 : %s operation failed
  • ora-12642 : No session key
  • ora-16796 : one or more properties could not be imported from the database
  • ora-24028 : cannot create a reciever non-repudiable single consumer queue
  • ora-01033 : ORACLE initialization or shutdown in progress
  • ora-01947 : TEMPORARY TABLESPACE already specified
  • ora-15007 : name is already used by an existing template
  • ora-09804 : Class conversion from binary to ORACLE failed.
  • ora-12562 : TNS:bad global handle
  • 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.