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

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-06130 : NETTCP: host access denied
  • ora-32009 : cannot reset the memory value for instance string from instance string
  • ora-02253 : constraint specification not allowed here
  • ora-33270 : (DBERR05) Analytic workspace string already exists.
  • ora-12451 : label not designated as USER or DATA
  • ora-33309 : (DBVALID05) SEVERE ERROR: Record number used but not allocated (PS number)
  • ora-27023 : skgfqsbi: media manager protocol error
  • ora-06812 : TLI Driver: could not read the ethernet driver's node address
  • ora-01543 : tablespace 'string' already exists
  • ora-08110 : Oracle event to test SMON cleanup for online index build
  • ora-31412 : change set string is disabled and cannot be advanced
  • ora-16402 : ONDEMAND archival requires FAL_CLIENT and FAL_SERVER support
  • ora-39785 : SQL expressions returning ADT objects are not allowed in direct path
  • ora-06538 : statement violates string RESTRICT_REFERENCES pragma
  • ora-23469 : %s is different between templates
  • ora-31644 : unable to position to block number string in dump file "string"
  • ora-00334 : archived log: 'string'
  • ora-13712 : Cannot perform ADDM analysis on AWR snapshots from previous releases. Snapshot version "string" do not match the database version "string".
  • ora-13024 : polygon has less than three segments
  • ora-12815 : value for INSTANCES must be greater than 0
  • ora-01083 : value of parameter "string" is inconsistent with that of other instances
  • ora-16057 : DGID from server not in Data Guard configuration
  • ora-29505 : AS keyword is invalid in CREATE JAVA CLASS or RESOURCE
  • ora-00253 : character limit string exceeded by archive destination string string
  • ora-16711 : the resource guard index is out of bounds
  • ora-39099 : cannot create index for "string" on master table string
  • ora-16600 : failover operation can only be submitted at target database
  • ora-32411 : materialized view definition query exceeds the maximum length
  • ora-16526 : unable to allocate task element
  • ora-01659 : unable to allocate MINEXTENTS beyond string in tablespace string
  • 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.