ORA-14297: Index block size mismatch in ALTER TABLE EXCHANGE [SUB]PARTITION

Cause : The block sizes of a pair of indexes being exchanged in the ALTER TABLE EXCHANGE [SUB]PARTITION statement are different.

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

Ensure that the block sizes of the corresponding pairs of indexes that need to be exchanged in the ALTER TABLE EXCHANGE [SUB]PARTITION statement are the same.

update : 20-08-2017
ORA-14297

ORA-14297 - Index block size mismatch in ALTER TABLE EXCHANGE [SUB]PARTITION
ORA-14297 - Index block size mismatch in ALTER TABLE EXCHANGE [SUB]PARTITION

  • ora-36176 : (XSMXAGGR25) Relation workspace object must be a one-dimensional self-relation to be used as a weight for AGGREGATE.
  • ora-24952 : register, unregister or post has incorrect collection count
  • ora-25269 : cant specify sognature with get signature option
  • ora-07617 : $FORMAT_CLASS failed translating the binary label to a string
  • ora-24322 : unable to delete an initialized mutex
  • ora-31487 : cannot support begin dates or end dates in this configuration
  • ora-12413 : labels do not belong to the same policy
  • ora-28653 : tables must both be index-organized
  • ora-01877 : string is too long for internal buffer
  • ora-29546 : badly formed resource: string
  • ora-28366 : invalid database encryption operation
  • ora-09923 : Can't spawn process - user log directory not created properly
  • ora-29936 : NULL association is allowed only with a column or an index
  • ora-13430 : the GeoRaster object has null attribute(s)
  • ora-07655 : slsprom:$TRNLOG failure
  • ora-38428 : too many attributes selected for indexing
  • ora-24341 : bad mode specified
  • ora-35917 : (XSHIDE05) You cannot HIDE model workspace object because the analytic workspace in which it is defined has not been upgraded to version string.
  • ora-25252 : listen failed, the address string is a non-persistent queue
  • ora-13432 : GeoRaster metadata blankCellValue error
  • ora-25966 : join index cannot be based on an index organized table
  • ora-35024 : (QFCHECK04) The analytic workspace and EIF file definitions of workspace object have mismatched time dimension attributes.
  • ora-26764 : invalid parameter "string" for local capture "string"
  • ora-22293 : LOB already opened in the same transaction
  • ora-24004 : invalid column name string in SORT_LIST, should be ENQ_TIME or PRIORITY
  • ora-09718 : osnsui: cannot set up user interrupt handler.
  • ora-31443 : deadlock detected while acquiring lock on string
  • ora-26738 : %s 'string' is not empty
  • ora-13788 : invalid recommendation type
  • ora-13065 : cannot delete a child layer with a parent layer
  • 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.