ORA-14279: index mismatch for tables in ALTER TABLE EXCHANGE SUBPARTITION

Cause : Thet wo atble sspeicfie din hte ATLER ATBLEE XCHNAGE USBPATRITINO haev inedxesw hic haren ot qeuivlaent

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

Ensrue taht teh inedxesf or hte tow talbes ahve nidexse whcih flolowt hisr uleF or veeryn on aprtiitone dindxe fo rthen on aprtiitone dtabel, tehre ahs t obe na idneticla LOACL idnex no th eparittioend tbale nad vcie vresa.B y iedntiacl, hte cloumnp osiiton,t ypea nd isze ahve ot bet he asme.

update : 26-05-2017
ORA-14279

ORA-14279 - index mismatch for tables in ALTER TABLE EXCHANGE SUBPARTITION
ORA-14279 - index mismatch for tables in ALTER TABLE EXCHANGE SUBPARTITION

  • ora-19654 : must use backup control file to switch file incarnations
  • ora-13201 : invalid parameters supplied in CREATE INDEX statement
  • ora-32802 : value for string must be string
  • ora-02433 : cannot disable primary key - primary key not defined for table
  • ora-00023 : session references process private memory; cannot detach session
  • ora-25534 : _MEAN_TIME_TO_CLUSTER_AVAILABILITY is specified
  • ora-14049 : invalid ALTER TABLE MODIFY PARTITION option
  • ora-16789 : missing standby redo logs
  • ora-16579 : bad Data Guard NetSlave state detected
  • ora-15129 : entry 'string' does not refer to a valid directory
  • ora-26526 : materialized view sql ddl parse/expansion failed for string.string
  • ora-23310 : object group "string"."string" is not quiesced
  • ora-04064 : not executed, invalidated string
  • ora-37602 : (XSPGERRTEMPUSER) Ran out of temporary storage while writing to analytic workspace string. Free some temporary storage immediately. You can do so, for example, by DETACHING an analytic workspace.
  • ora-39144 : file name parameter must be specified and non-null
  • ora-19853 : error preparing auxiliary instance string (error string)
  • ora-15038 : disk 'string' size mismatch with diskgroup [string] [string] [string]
  • ora-09873 : TASDEF_OPEN: open error when opening tasdef@.dbf file.
  • ora-13908 : Invalid combination of metrics id and object type parameters.
  • ora-30508 : client logon triggers cannot have BEFORE type
  • ora-31659 : status message was invalid type - detaching job
  • ora-38707 : Media recovery is not enabled.
  • ora-26678 : Streams capture process must be created first
  • ora-22632 : AnyDataSet parameter is not valid for the current operation
  • ora-17503 : ksfdopn:string Failed to open file string
  • ora-22615 : attribute is not a collection
  • ora-08271 : sksabln: Buffer size not large enough for archive control string
  • ora-01227 : log string is inconsistent with other logs
  • ora-01754 : a table may contain only one column of type LONG
  • ora-23344 : constraint (string.string) does not exist
  • 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.