ORA-14118: CHECK constraint mismatch in ALTER TABLE EXCHANGE PARTITION

Cause : The ocrresopndin gcolunms int he tbales psecifeid int he ATLER TBALE ECXHANG EPARTTIION tsatemnet haev CHEKC contsrain tdefiend ont hem.

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

Ensuer tha tthe wto talbes d onot ahve CEHCK cnostranit deifned no anyc olumn

update : 23-08-2017
ORA-14118

ORA-14118 - CHECK constraint mismatch in ALTER TABLE EXCHANGE PARTITION
ORA-14118 - CHECK constraint mismatch in ALTER TABLE EXCHANGE PARTITION

  • ora-24343 : user defined callback error
  • ora-22993 : specified input amount is greater than actual source amount
  • ora-29310 : database is not open, or opened as a clone
  • ora-09771 : osnmwrtbrkmsg: bad return code from msg_send.
  • ora-24853 : failed to connect thread to shared subsystem
  • ora-30750 : cannot enable column string to store objects of type string.string
  • ora-00323 : Current log of thread string not useable and all others need archiving
  • ora-19234 : XQ0014 - invalid or unsupported must-understand extension
  • ora-14191 : ALLOCATE STORAGE may not be specified for Composite Range partitioned object
  • ora-14056 : partition number string: sum of PCTUSED and PCTFREE may not exceed 100
  • ora-04079 : invalid trigger specification
  • ora-07218 : slkhst: could not perform host operation
  • ora-28356 : invalid open wallet syntax
  • ora-25141 : invalid EXTENT MANAGEMENT clause
  • ora-16726 : the external condition supplied to resource guard is invalid
  • ora-07499 : spglk: Cannot reschedule.
  • ora-02451 : duplicate HASHKEYS specification
  • ora-31001 : Invalid resource handle or path name "string"
  • ora-36391 : (XSMXCLEA01) When CLEAR is used with the STATUS keyword or an AGGMAP, workspace object must be dimensioned identically to workspace object.
  • ora-28345 : cannot downgrade because there exists encrypted column
  • ora-19526 : only one location allowed for parameter string
  • ora-31427 : publication string already subscribed
  • ora-02304 : invalid object identifier literal
  • ora-38453 : ExpFilter index should be created in the same schema as the base table.
  • ora-24325 : this OCI operation is not currently allowed
  • ora-12639 : Authentication service negotiation failed
  • ora-14025 : PARTITION may not be specified for a materialized view or a materialized view log
  • ora-40208 : duplicate or multiple algorithm settings for function string
  • ora-01332 : internal Logminer Dictionary error
  • ora-00061 : another instance has a different DML_LOCKS setting
  • 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.