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 : 27-04-2017

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

  • ora-30118 : syntax error at 'string' at the end of input
  • ora-08235 : smsget: listener not on this node
  • ora-13907 : Threshold value is invalid.
  • ora-01266 : Unable to create unique file name
  • ora-39104 : cannot call this function from a SQL parallel query slave process
  • ora-02047 : cannot join the distributed transaction in progress
  • ora-31480 : staging database and source database cannot be the same
  • ora-18015 : invalid source outline signature
  • ora-30486 : invalid window aggregation group in the window specification
  • ora-01317 : Not attached to a Logminer session
  • ora-23333 : column string is already part of a column group
  • ora-37001 : You have one or more attached but unupdated analytic workspaces.
  • ora-22979 : cannot INSERT object view REF or user-defined REF
  • ora-26742 : Maximum number of ignored transactions exceeded
  • ora-13853 : Tracing for service (module/action) string is already enabled
  • ora-00200 : control file could not be created
  • ora-14081 : new partition name must differ from the old partition name
  • ora-02243 : invalid ALTER INDEX or ALTER MATERIALIZED VIEW option
  • ora-00269 : specified log file is part of thread string not string
  • ora-03127 : no new operations allowed until the active operation ends
  • ora-16716 : clearing parameter LOG_ARCHIVE_DEST failed
  • ora-39180 : unable to encrypt ENCRYPTION_PASSWORD
  • ora-24353 : user buffer too small to accommodate COBOL display type
  • ora-32301 : object-relational materialized views must be primary key based
  • ora-19234 : XQ0014 - invalid or unsupported must-understand extension
  • ora-32640 : FOR LIKE loops are not allowed for multi-byte character types
  • ora-22294 : cannot update a LOB opened in read-only mode
  • ora-28108 : circular security policies detected
  • ora-09981 : skxfqdreg: Error Adding a page to the SDI buffer pool
  • ora-30726 : cannot specify referenced column list here
  • 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.