ORA-25132: UNIQUE constraint (string.string) disabled and validated in ALTER TABLE EXCHANGE PARTITION

Cause : cannot ALTER TABLE EXCHANGE PARTITION when the partition and the table have a disabled and validated unique constraints AND the unique keys in the partion is not mutually exclusive from the rest of the table.

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

Change the constraint's status.

update : 21-07-2017

ORA-25132 - UNIQUE constraint (string.string) disabled and validated in ALTER TABLE EXCHANGE PARTITION
ORA-25132 - UNIQUE constraint (string.string) disabled and validated in ALTER TABLE EXCHANGE PARTITION

  • ora-31015 : Attempted to insert entry without name
  • ora-12044 : invalid CREATE MATERIALIZED VIEW LOG option
  • ora-30736 : objects in a table or view hierarchy have to be in the same schema
  • ora-13228 : spatial index create failed due to invalid type
  • ora-02258 : duplicate or conflicting NULL and/or NOT NULL specifications
  • ora-00267 : name of archived log file not needed
  • ora-01292 : no log file has been specified for the current LogMiner session
  • ora-12680 : Native services disabled but required
  • ora-31456 : error executing a procedure in the DBMS_CDC_UTILITY package
  • ora-19862 : backup pieces must be validated before accessing results
  • ora-02367 : file truncated error in string
  • ora-19202 : Error occurred in XML processingstring
  • ora-12419 : null binary label value
  • ora-12041 : cannot record ROWIDs for index-organized table "string"."string"
  • ora-32406 : cannot alter partitioning for existing materialized view log
  • ora-29888 : cannot create domain index on a table with row movement enabled
  • ora-01487 : packed decimal number too large for supplied buffer
  • ora-02713 : osnprd: message receive failure
  • ora-00486 : ASMB process terminated with error
  • ora-32827 : Messaging Gateway agent must be shut down
  • ora-31477 : could not detach LogMiner session during cleanup
  • ora-22328 : object "string"."string" has errors. string
  • ora-14603 : [SUBPARTITIONS | SUBPARTITION TEMPLATE] subpartition_count syntax is valid only for range-hash tables
  • ora-38726 : Flashback database logging is not on.
  • ora-00203 : using the wrong control files
  • ora-01504 : database name 'string' does not match parameter db_name 'string'
  • ora-31045 : Cannot store more than string extras outside the root XML node
  • ora-36181 : A VARIABLE cannot have both the $AGGREGATE_FROM and $AGGREGATE_FROMVAR properties applied to it.
  • ora-19332 : Invalid column in the CREATE_DBURI operator
  • ora-00108 : failed to set up dispatcher to accept connection asynchronously
  • 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.