ORA-24805: LOB type mismatch

Cause : When copying or appending LOB locators, both source and desctination LOB locators should be of the same type.

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

Pass the same type of LOB locators for copying or appending.

update : 21-08-2017

ORA-24805 - LOB type mismatch
ORA-24805 - LOB type mismatch

  • ora-39314 : call to DBMS_SCHEMA_COPY.SYNC_CODE is not legal
  • ora-13342 : an arc geometry has fewer than three coordinates
  • ora-13152 : invalid HHCODE type
  • ora-00337 : log file 'string' does not exist and no size specified
  • ora-38303 : invalid option for PURGE TABLESPACE
  • ora-23301 : mixed use of deferred rpc destination modes
  • ora-07602 : spgto: $GETJPIW failure
  • ora-02822 : Invalid block offset
  • ora-19323 : Invalid url string
  • ora-19010 : Cannot insert XML fragments
  • ora-30448 : internal data of the advisor repository is inconsistent
  • ora-19851 : OS error while managing auxiliary database string
  • ora-26103 : V6 or V7 data file used to create control file
  • ora-37003 : (AWLISTALL01) number readers
  • ora-00083 : warning: possibly corrupt SGA mapped
  • ora-31451 : invalid value string for capture_values, expecting: OLD, NEW, or BOTH
  • ora-31659 : status message was invalid type - detaching job
  • ora-24501 : invalid UTF16 string passed in
  • ora-19375 : no CREATE TABLE privilege on schema "string"
  • ora-00372 : file string cannot be modified at this time
  • ora-14104 : RECOVERABLE/UNRECOVERABLE may not be specified for partitioned tables/indices
  • ora-13239 : sdo_dimensionality not specified during n-d R-tree creation
  • ora-25187 : specified exceptions table form incorrect
  • ora-23303 : application raised generic exception during deferred RPC
  • ora-29327 : unsupported client compatibility mode used when talking to the server
  • ora-08101 : index key does not exist file string: (root string, node string) blocks (string)
  • ora-30134 : reserved for future use
  • ora-16168 : LGWR network server could not switch to blocking mode
  • ora-02185 : a token other than WORK follows COMMIT
  • ora-01772 : Must specify a value for LEVEL
  • 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.