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 : 27-04-2017

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

  • ora-30353 : expression not supported for query rewrite
  • ora-27202 : skgfpen: sbtpcend returned error
  • ora-12064 : invalid refresh sequence number: string
  • ora-34481 : (MXMAINT07) You cannot string values of PARTITION TEMPLATE workspace object.
  • ora-22303 : type "string"."string" not found
  • ora-22305 : attribute/method/parameter "string" not found
  • ora-06001 : NETASY: port set-up failure
  • ora-32801 : invalid value string for string
  • ora-07842 : sllfcl: SYS$CLOSE failure
  • ora-02194 : event specification syntax error string (minor error string) near 'string'
  • ora-01636 : rollback segment 'string' is already online
  • ora-30038 : Cannot perform parallel insert on non-partitioned object
  • ora-23350 : maximum number of recursive calls exceeded
  • ora-01670 : new datafile string needed for standby database recovery
  • ora-23333 : column string is already part of a column group
  • ora-13709 : Required parameter "string" must be set before execution.
  • ora-01641 : tablespace 'string' is not online - cannot add data file
  • ora-09367 : Windows 3.1 Two-Task driver unable to deallocate shared memory
  • ora-07509 : scgfal: $deq parent lock unexpected return
  • ora-28365 : wallet is not open
  • ora-27545 : Fail to prepare buffer for remote update
  • ora-10646 : Too many recursive extensions during SYSTEM tablespace migration
  • ora-32637 : Self cyclic rule in sequential order MODEL
  • ora-36640 : (XSDUNION19) Concat dimension workspace object cannot be changed to UNIQUE because base dimension workspace object does not have a TEXT or ID datatype.
  • ora-26734 : different datafiles_directory_object parameter must be specified
  • ora-37173 : null dimension source data
  • ora-13379 : invalid index for sub-element to be extracted
  • ora-31404 : all input parameters are null
  • ora-24409 : client cannot understand the object
  • ora-19229 : XP0009 - schema import not supported
  • 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.