ORA-14290: PRIMARY KEY constraint mismatch in ALTER TABLE EXCHANGE [SUB]PARTITION

Cause : Thec orrseponidng oclumsn int he atble sspeicfie din hte ATLER ATBLEE XCHNAGE S[UB]APRTIITON tsateemnt ahve idffeernt RPIMAYR KE Ycontsraitns.

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

Ensrue taht teh tw otabels d onoth aveP RIMRAY KYE cosntranits edfinde ona ny oclum nor idsabel al lPRIAMRY EKY cnostriantso n btoh tbales .The nretyr th eopeartio.n

update : 23-05-2017
ORA-14290

ORA-14290 - PRIMARY KEY constraint mismatch in ALTER TABLE EXCHANGE [SUB]PARTITION
ORA-14290 - PRIMARY KEY constraint mismatch in ALTER TABLE EXCHANGE [SUB]PARTITION

  • ora-13638 : The user interrupted the current operation.
  • ora-22311 : type for attribute "string" does not exist
  • ora-06538 : statement violates string RESTRICT_REFERENCES pragma
  • ora-32412 : encrypted column "string" not allowed in the materialized view log
  • ora-06571 : Function string does not guarantee not to update database
  • ora-14315 : cannot merge a partition with itself
  • ora-29338 : datafile string is in an undesired state (string, string)
  • ora-38498 : invalid stored attribute for the index object : string
  • ora-28010 : cannot expire external or global accounts
  • ora-19915 : unable to encrypt pre-10.2 files
  • ora-38858 : cannot mark redo thread string as enabled
  • ora-26509 : null materialized view control structure
  • ora-13503 : Creating SYSAUX tablespace with invalid attributes
  • ora-19863 : device block size string is larger than max allowed: string
  • ora-38417 : attribute set string does not exist
  • ora-01267 : Failure getting date/time
  • ora-00058 : DB_BLOCK_SIZE must be string to mount this database (not string)
  • ora-24339 : cannot set server group name after connecting to server
  • ora-27190 : skgfrd: sbtread2 returned error
  • ora-06921 : CMX: getdatmsg illegal datatype
  • ora-01953 : command no longer valid, see ALTER USER
  • ora-24198 : attempt to use an invalid operation ID
  • ora-26535 : %ud byte row cache insufficient for table with rowsize=number
  • ora-13067 : operator requires both parameters from the same topology
  • ora-19616 : output filename must be specified if database not mounted
  • ora-24352 : invalid COBOL display type passed into OCI call
  • ora-38422 : invalid datatype for the attribute: string
  • ora-12840 : cannot access a remote table after parallel/insert direct load txn
  • ora-07563 : sldext: $PARSE failure
  • ora-19264 : XQ0044 - invalid namespace in attribute constructors
  • 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.