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 : 24-06-2017
ORA-14296

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-28662 : IOT index and overflow segments must share the same LOGGING attribute
  • ora-29268 : HTTP client error string
  • ora-09853 : snyRemovePort: bad return code from request.
  • ora-24345 : A Truncation or null fetch error occurred
  • ora-25119 : LOGGING/NOLOGGING option already specified
  • ora-01870 : the intervals or datetimes are not mutually comparable
  • ora-24810 : attempting to write more data than indicated
  • ora-06902 : CMX: cannot attach to cmx subsystem
  • ora-15008 : cannot drop system template
  • ora-27041 : unable to open file
  • ora-30443 : definition for filter string's item string is invalid
  • ora-31497 : invalid value specified for first_scn
  • ora-01953 : command no longer valid, see ALTER USER
  • ora-27196 : skgfpbk: sbtpcbackup returned error
  • ora-27003 : cannot open file on device allocated with NOIO option
  • ora-12731 : invalid collation class in regular expression
  • ora-13067 : operator requires both parameters from the same topology
  • ora-13527 : invalid baseline name
  • ora-30399 : a skip level must have at least one column that allows NULL values
  • ora-19033 : schema specified in the XML document does not match the schema parameter
  • ora-22061 : invalid format text [string]
  • ora-01254 : cannot end online backup - file string in recovery manager backup
  • ora-30334 : illegal dimension level name
  • ora-30969 : invalid syntax for PARAMETERS
  • ora-28007 : the password cannot be reused
  • ora-13113 : invalid tg_layer_id in sdo_topo_geometry constructor
  • ora-31167 : XML nodes over 64K in size cannot be inserted
  • ora-39767 : finish is not allowed when unloaded stream data exists
  • ora-14189 : this physical attribute may not be specified for an index subpartition
  • ora-24440 : OCI Easy Install mode cannot be initialized
  • 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.