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

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

  • ora-13051 : failed to initialize spatial object
  • ora-06505 : PL/SQL: variable requires more than 32767 bytes of contiguous memory
  • ora-07503 : scgcmn: $setimr unexpected return
  • ora-16235 : DDL skipped because import has occurred
  • ora-16211 : unsupported record found in the archived redo log
  • ora-26726 : logical standby and DOWNSTREAM_REAL_TIME_MINE are incompatible
  • ora-15122 : ASM file name 'string' contains an invalid file number
  • ora-12048 : error encountered while refreshing materialized view "string"."string"
  • ora-19720 : Error occurred when converting an OCI number into an SCN
  • ora-02396 : exceeded maximum idle time, please connect again
  • ora-14106 : LOGGING/NOLOGGING may not be specified for a clustered table
  • ora-39160 : error on whats my name call
  • ora-01864 : the date is out of range for the current calendar
  • ora-19691 : %s is from different database: id=string, name=string
  • ora-02050 : transaction string rolled back, some remote DBs may be in-doubt
  • ora-29821 : specified primary operator does not exist
  • ora-08342 : sropen: failed to open a redo server connection
  • ora-12489 : default label not within clearance range
  • ora-31411 : change set string is referenced by a change table
  • ora-28201 : Not enough privileges to enable application role 'string'
  • ora-37011 : (XSACQUIRE_LOCKED) Object workspace object is locked by another user.
  • ora-34489 : (MXMAINT06) You cannot maintain workspace object because it is a SURROGATE.
  • ora-07239 : slemrd: invalid file handle, seals do not match.
  • ora-01506 : missing or illegal database name
  • ora-19267 : XQ0047 - module string not found
  • ora-24436 : Invalid statement Handle.
  • ora-12166 : TNS:Client can not connect to HO agent.
  • ora-16206 : database already configured as Logical Standby database
  • ora-40101 : Data Mining System Error string-string-string
  • ora-08120 : Need to create SYS.IND_ONLINE$ table in order to (re)build index
  • 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.