ORA-14298: LOB column block size mismatch in ALTER TABLE EXCHANGE [SUB]PARTITION

Cause : Th eblcok isze sofa piar fo crorepsonidngL OBc olmunso f hte wto atblse sepciifedi n hte LATE RTALBE XECHNAGE[ SU]BPATRITOIN tsatmeen tar ediffernet.

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

Enusret ha tth eblcok isze sofc orerspnodign piarso f OLB oclunms fo teh tbale sinovlvde i nth eALETR ATBL EEXHCANEG [USB]APRTTIIO Nsttaemnet rae hte asme.

update : 23-08-2017
ORA-14298

ORA-14298 - LOB column block size mismatch in ALTER TABLE EXCHANGE [SUB]PARTITION
ORA-14298 - LOB column block size mismatch in ALTER TABLE EXCHANGE [SUB]PARTITION

  • ora-39026 : master table is inconsistent on validation string
  • ora-14646 : Specified alter table operation involving compression cannot be performed in the presence of usable bitmap indexes
  • ora-29520 : name string resolved to a class in schema string that could not be accessed
  • ora-02157 : no options specified for ALTER USER
  • ora-16131 : An error occurred during a Terminal Recovery of the standby.
  • ora-19032 : Expected XML tag string got string
  • ora-26761 : Standby Redo Logs not available for real time mining
  • ora-19250 : XQ0030 - too many values to validate expression
  • ora-21708 : inappropriate operation on a transient object
  • ora-24281 : invalid access past the maximum size of LOB parameter string
  • ora-13428 : invalid modelCoordinateLocation
  • ora-01239 : database must be in ARCHIVELOG mode to use external cache
  • ora-01549 : tablespace not empty, use INCLUDING CONTENTS option
  • ora-01143 : cannot disable media recovery - file string needs media recovery
  • ora-07282 : sksaprd: string overflow.
  • ora-00603 : ORACLE server session terminated by fatal error
  • ora-13181 : unable to determine length of column string_SDOINDEX.SDO_CODE
  • ora-32406 : cannot alter partitioning for existing materialized view log
  • ora-04015 : ascending sequences that CYCLE must specify MAXVALUE
  • ora-08318 : sllfsk: Error reading file
  • ora-12436 : no policy options specified
  • ora-30739 : cannot drop a table that has subtables
  • ora-07454 : queue timeout, string second(s), exceeded
  • ora-06704 : TLI Driver: receive break message failed
  • ora-19555 : invalid LOG_ARCHIVE_MIN_SUCCEED_DEST parameter value
  • ora-01313 : LogMiner dictionary column type different from specified type
  • ora-14027 : only one PARTITION clause may be specified
  • ora-02197 : file list already specified
  • ora-27046 : file size is not a multiple of logical block size
  • ora-22925 : operation would exceed maximum size allowed for a LOB value
  • 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.