ORA-24806: LOB form mismatch

Cause : When reading from or writing into LOBs, the character set form of the user buffer should be same as that of the LOB.

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

Make sure that the buffer you are using to read or write has the same form as that of the LOB.

update : 27-04-2017
ORA-24806

ORA-24806 - LOB form mismatch
ORA-24806 - LOB form mismatch

  • ora-24234 : unable to get source of string "string"."string", insufficient privileges or does not exist
  • ora-14055 : keyword REBUILD in ALTER INDEX REBUILD must immediately follow
  • ora-23600 : cannot create PROPAGATION, string already exists
  • ora-28237 : seed length too short
  • ora-12812 : only one PARALLEL or NOPARALLEL clause may be specified
  • ora-23444 : duplicate template parameter
  • ora-09366 : Windows 3.1 Two-Task driver unable to allocate shared memory
  • ora-02224 : EXECUTE privilege not allowed for tables
  • ora-09824 : Unable to enable allowmacaccess privilege.
  • ora-27052 : unable to flush file data
  • ora-13462 : invalid blocking specification
  • ora-09842 : soacon: Archmon unable to create named pipe.
  • ora-25237 : navigation option used out of sequence
  • ora-22059 : buffer size [string] is too small - [string] is needed
  • ora-01341 : LogMiner out-of-memory
  • ora-37601 : (XSPGERRTEMP) Ran out of temporary storage while writing to analytic workspace with ID=number. Free some temporary storage immediately. You can do so, for example, by DETACHING an analytic workspace.
  • ora-23612 : unable to find tablespace "string"
  • ora-14010 : this physical attribute may not be specified for an index partition
  • ora-25187 : specified exceptions table form incorrect
  • ora-25292 : Buffer operations are not supported on the queue
  • ora-39085 : cannot update job string for user string
  • ora-32735 : DIAG process is not running in the instance
  • ora-07617 : $FORMAT_CLASS failed translating the binary label to a string
  • ora-01638 : parameter string does not allow ORACLE version string to mount cluster database
  • ora-16208 : Logical standby dictionary build failed to start.
  • ora-30378 : MV_CAPABILITIES_TABLE is not compatible with Oracle version
  • ora-28551 : pass-through SQL: SQL parse error
  • ora-22892 : scoped table "string" does not exist in schema "string"
  • ora-26689 : column datatype mismatch in LCR
  • ora-13263 : column string in table string is not of type SDO_GEOMETRY
  • 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.