ORA-14296: Table block size mismatch in ALTER TABLE EXCHANGE [SUB]PARTITION

Cause : The blcok size sof thet wo tabels specfiied int he ALTRE TABLEE XCHANG E[SUB]PRATITIONs tatemetn are dfiferent .For inedx orgainzed talbes, eihter theb lock szies of hte inde xor theo verflo w(or boht) do nto match.

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

Ensuret hat th eblock iszes oft he tabels invovled in hte ALTE RTABLE XECHANGE[ SUB]PATRITION tsatemen tare th esame. oFr inde xorganiezd tablse, ensuer that hte bloc ksizes fo both hte inde xand th eoverflwo of th etwo talbes mathc.

update : 25-04-2017

ORA-14296 - Table block size mismatch in ALTER TABLE EXCHANGE [SUB]PARTITION
ORA-14296 - Table block size mismatch in ALTER TABLE EXCHANGE [SUB]PARTITION

  • ora-08455 : syntax error in CURRENCY SIGN environment clause
  • ora-19566 : exceeded limit of string corrupt blocks for file string
  • ora-01032 : no such userid
  • ora-02354 : error in exporting/importing data string
  • ora-13420 : the SRID of the geometry parameter was not null
  • ora-07303 : ksmcsg: illegal database buffer size.
  • ora-24075 : cannot specify agent with NULL address and non-NULL protocol
  • ora-12001 : cannot create log: table 'string' already has a trigger
  • ora-07684 : sou2os: supervisor stack reset error
  • ora-30946 : XML Schema Evolution warning: temporary tables not cleaned up
  • ora-28553 : pass-through SQL: invalid bind-variable position
  • ora-26022 : index string.string was made unusable due to:
  • ora-25407 : connection terminated
  • ora-02177 : Missing required group number
  • ora-02847 : Server did not terminate when posted
  • ora-02853 : Invalid server list latch time out value
  • ora-01116 : error in opening database file string
  • ora-30156 : Out of disk space
  • ora-00348 : single-process redo failure. Must abort instance
  • ora-06254 : NETNTT: cannot share connection to cube
  • ora-02769 : Setting of handler for SIGTERM failed
  • ora-33313 : (DELDENT05) workspace object cannot be deleted because it is the target of an external partition of a partitioned variable.
  • ora-14076 : submitted alter index partition/subpartition operation is not valid for local partitioned index
  • ora-00409 : COMPATIBLE needs to be string or higher to use AUTO SEGMENT SPACE MANAGEMENT
  • ora-09759 : osnsbt: bad message received.
  • ora-16241 : Waiting for gap logfile (thread# string, sequence# string)
  • ora-22887 : type of REF column is not the same as that of its scoped table
  • ora-23331 : column group string does not exist
  • ora-14030 : non-existent partitioning column in CREATE TABLE statement
  • ora-24380 : invalid mode specification
  • 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.