ORA-14131: enabled UNIQUE constraint exists on one of the tables

Cause : One of the tables referenced in the ALTER TABLE EXCHANGE PARTITION|SUBPARTITION statement has enabled UNIQUE constraint(s) defined on it, which prevents EXCHANGE from proceeding.

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

Disable constraints defined on tables referenced in the ALTER TABLE EXCHANGE PARTITION|SUBPARTITION statement and retry the statement.

update : 23-06-2017

ORA-14131 - enabled UNIQUE constraint exists on one of the tables
ORA-14131 - enabled UNIQUE constraint exists on one of the tables

  • ora-14511 : cannot perform operation on a partitioned object
  • ora-23325 : parameter type is not string
  • ora-28006 : conflicting values for parameters string and string
  • ora-01652 : unable to extend temp segment by string in tablespace string
  • ora-21700 : object does not exist or is marked for delete
  • ora-38491 : could not evaluate subexpression for rowid "string"
  • ora-30991 : cannot use DOM to add special attribute to schema-based parent
  • ora-13523 : unable to allocate required space for return type
  • ora-22335 : The client cannot work with an altered type
  • ora-12851 : PARALLEL_MAX_SERVERS must be greater than or equal to PARALLEL_MIN_SERVERS, string
  • ora-01637 : rollback segment 'string' is being used by another instance (#string)
  • ora-39057 : invalid worker request string for string jobs.
  • ora-09262 : spdde: error terminating detached (background) process
  • ora-07457 : cannot set _INTERNAL_RESOURCE_MANAGER_PLAN because of FORCE
  • ora-28164 : REVOKE already specified
  • ora-39314 : call to DBMS_SCHEMA_COPY.SYNC_CODE is not legal
  • ora-27369 : job of type EXECUTABLE failed with exit code: string
  • ora-34656 : (MXSQL24) Additional WHERE clause conditions with CURRENT OF syntax
  • ora-14286 : cannot COALESCE the only subpartition of this table partition
  • ora-16009 : remote archive log destination must be a STANDBY database
  • ora-00334 : archived log: 'string'
  • ora-15154 : cluster rolling upgrade incomplete
  • ora-24803 : illegal parameter value in lob read function
  • ora-33454 : (ESDREAD07) Discarding compiled code for workspace object because number is now string workspace object, whereas it was string workspace object when the code was compiled.
  • ora-07702 : unrecognized device type in archive text
  • ora-01928 : GRANT option not granted for all privileges
  • ora-31694 : master table string failed to load/unload
  • ora-25465 : variable name not specified
  • ora-14644 : table is not subpartitioned by Hash method
  • ora-30750 : cannot enable column string to store objects of type string.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.