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 : 29-06-2017

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

  • ora-23538 : cannot explicitly refresh a NEVER REFRESH materialized view ("string")
  • ora-29811 : missing STATISTICS keyword
  • ora-01538 : failed to acquire any rollback segment
  • ora-23453 : requested operation is not supported on top flavor
  • ora-07591 : spdde: $GETJPIW failure
  • ora-02094 : replication option not installed
  • ora-38406 : attribute set string already exists
  • ora-26500 : error on caching "string"."string"
  • ora-08237 : smsget: SGA region not yet created
  • ora-24123 : feature string is not yet implemented
  • ora-27250 : OS system call failure
  • ora-14305 : List value 'string' specified twice in partition 'string'
  • ora-31602 : parameter string value "string" in function string inconsistent with string
  • ora-07576 : sspexst: $GETJPIW failure on process ID string
  • ora-37129 : (XSCCOMP04) Cannot aggregate over COMPRESSED COMPOSITE workspace object using AGGMAP workspace object. All static MODEL statements must precede all RELATION statements over the bases of the COMPRESSED COMPOSITE.
  • ora-23414 : materialized view log for "string"."string" does not record rowid values
  • ora-13222 : failed to compute supercell for geometry in string
  • ora-14624 : DEFAULT subpartition must be last subpartition specified
  • ora-14327 : Some index [sub]partitions could not be rebuilt
  • ora-00222 : operation would reuse name of a currently mounted control file
  • ora-35095 : (QFSVNS01) One or more imported values of fixed-width dimension workspace object have been truncated.
  • ora-19107 : invalid XQueryX - unsupported construct - string
  • ora-15152 : cluster in rolling upgrade
  • ora-10628 : Turn on sanity check for kdiss index skip scan state
  • ora-29379 : resource plan string is involved in a loop in top-plan string
  • ora-06556 : the pipe is empty, cannot fulfill the unpack_message request
  • ora-21615 : an OTS (named or simple) instance failed
  • ora-22329 : cannot alter a non-object type
  • ora-25125 : BUFFER_POOL storage option not allowed
  • ora-19905 : log_archive_format must contain %%s, %%t and %%r
  • 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.