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

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-02365 : error seeking in file: string
  • ora-15170 : cannot add entry 'string' in directory 'string'
  • ora-01559 : MAXEXTENTS for rollback segment must be greater than 1
  • ora-12950 : SYSTEM tablespace specified as default permanent tablespace
  • ora-22863 : synonym for datatype string.string not allowed
  • ora-38487 : FUNCTION/PACKAGE/TYPE "string" not allowed in the expression
  • ora-15034 : disk 'string' does not require the FORCE option
  • ora-13410 : invalid layerNumbers or bandNumbers parameter
  • ora-12561 : TNS:unknown error
  • ora-38448 : Indexing predicates with "string" operator is not supported.
  • ora-29953 : cannot issue DDL on a domain index partition marked as FAILED
  • ora-13147 : failed to generate MBR
  • ora-29973 : Unsupported query or operation during change notification registration
  • ora-19661 : datafile string could not be verified
  • ora-23293 : Cannot rename a column which is part of a join index
  • ora-25303 : Buffered operation allowed only on the owner instance
  • ora-24361 : basic bind call not invoked before invoking advanced bind call
  • ora-01683 : unable to extend index string.string partition string by string in tablespace string
  • ora-36674 : (XSDPART12) Invalid dimension value starting at string.
  • ora-28120 : driving context already exists
  • ora-13404 : invalid ultCoordinate parameter
  • ora-14260 : incorrect physical attribute specified for this partition
  • ora-36165 : (XSAGGCNTPROP) Variable workspace object cannot have both an AGGCOUNT and the $COUNTVAR property.
  • ora-09712 : orasrv: log archiver already connected.
  • ora-36400 : (XSSPROP02) workspace object is not a valid variable name.
  • ora-34342 : (MXDSS01) IMPORTANT: Analytic workspace string is read-only. Therefore, you will not be able to use the UPDATE command to save changes to it.
  • ora-29823 : object being analyzed is not a table
  • ora-29518 : name string resolved to an object in schema string that is not a Java class
  • ora-12622 : TNS:event notifications are not homogeneous
  • ora-19902 : incarnation key string not found
  • 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.