ORA-24807: LOB form mismatch

Cause : When copying or appending LOBs, both source and desctination LOB locators should have the same character set form.

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

Pass locators of the same character set form for copying or appending LOBs.

update : 27-06-2017

ORA-24807 - LOB form mismatch
ORA-24807 - LOB form mismatch

  • ora-13016 : specified topology [string] is invalid
  • ora-32310 : object materialized views must select from an object table
  • ora-13635 : The value provided for parameter string cannot be converted to a number.
  • ora-31081 : name not specified for global declaration
  • ora-07472 : snclrd: open error when opening sgadef.dbf file.
  • ora-08430 : raw data missing leading sign
  • ora-24011 : cannot drop QUEUE, string should be stopped first
  • ora-33313 : (DELDENT05) workspace object cannot be deleted because it is the target of an external partition of a partitioned variable.
  • ora-00097 : use of Oracle SQL feature not in SQL92 string Level
  • ora-26713 : remote object does not exist or is inaccessible
  • ora-27146 : post/wait initialization failed
  • ora-26701 : STREAMS process string does not exist
  • ora-19209 : invalid or unsupported formatting argument
  • ora-32504 : expecting one of string, string, string, or string but found string
  • ora-38707 : Media recovery is not enabled.
  • ora-37132 : (XSCCOMP07) Incremental aggregation over the dense DIMENSION workspace object is not supported when aggregating a VARIABLE dimensioned by a COMPRESSED COMPOSITE.
  • ora-32635 : not a single cell reference predicate
  • ora-13144 : target table string not found
  • ora-36170 : (XSMXAGGR12) The data type of the WEIGHT workspace object must be numeric or BOOLEAN, not string.
  • ora-16643 : unable to determine location of broker configuration files
  • ora-12707 : error while getting create database NLS parameter string
  • ora-22333 : cannot reset type "string"."string" due to invalid dependent types and tables
  • ora-38951 : Target platform string not cross platform compliant
  • ora-29557 : Java system class string cannot be modified
  • ora-15109 : conflicting protection attributes specified
  • ora-02070 : database stringstring does not support string in this context
  • ora-01052 : required destination LOG_ARCHIVE_DUPLEX_DEST is not specified
  • ora-08178 : illegal SERIALIZABLE clause specified for user INTERNAL
  • ora-32625 : illegal dimension in cell reference predicate
  • ora-36962 : (XSRELTBL08) string is not a valid workspace object.
  • 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.