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 : 25-09-2017

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

  • ora-31624 : A job cannot be modified after it has started.
  • ora-23356 : masterdef recognizes a master which does not recognize the masterdef
  • ora-16148 : user requested expiration of managed recovery operation
  • ora-01554 : out of transaction slots in transaction tables
  • ora-30936 : Maximum number (string) of 'string' XML node elements exceeded
  • ora-38796 : Not enough flashback database log data to undo FLASHBACK.
  • ora-29352 : event 'string' is not an internal event
  • ora-21612 : key is already being used
  • ora-29550 : Java session state cleared
  • ora-01241 : an external cache has died
  • ora-02202 : no more tables permitted in this cluster
  • ora-25223 : user_data type used is not supported
  • ora-22341 : cannot assign supertype instance to subtype
  • ora-10588 : Can only allow 1 corruption for normal media/standby recovery
  • ora-03219 : Tablespace 'string' is dictionary-managed, offline or temporary
  • ora-26709 : Streams RFS restart
  • ora-16721 : unable to set LOG_ARCHIVE_DEST_n initialization parameters
  • ora-32058 : operation restricted to SYSDBA users
  • ora-12489 : default label not within clearance range
  • ora-34802 : (OCI11) OLAP OCI operation caused ROLLBACK past an UPDATE of an attached analytic workspace. Current operation canceled.
  • ora-07615 : $CHANGE_CLASS failed in retrieving the specified file label
  • ora-38795 : warning: FLASHBACK succeeded but OPEN RESETLOGS would get error below
  • ora-02423 : schema name does not match schema authorization identifier
  • ora-16013 : log string sequence# string does not need archiving
  • ora-00080 : invalid global area specified by level string
  • ora-29338 : datafile string is in an undesired state (string, string)
  • ora-09702 : sem_acquire: cannot acquire latch semaphore
  • ora-24132 : table name string is too long
  • ora-01909 : REUSE keyword expected
  • ora-06952 : Remote end of the communication issued a forward-reset packet.
  • 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.