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

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

  • ora-15180 : Could not open dynamic library string, error [string]
  • ora-25148 : ONLINE option not permitted
  • ora-29821 : specified primary operator does not exist
  • ora-13759 : User "string" cannot remove reference "string".
  • ora-01126 : database must be mounted in this instance and not open in any instance
  • ora-19562 : file string is empty
  • ora-12622 : TNS:event notifications are not homogeneous
  • ora-28173 : certificate not provided by proxy
  • ora-01231 : cannot make read write - file string is offline
  • ora-02446 : CREATE TABLE ... AS SELECT failed - check constraint violated
  • ora-19811 : cannot have files in DB_RECOVERY_FILE_DEST with keep attributes
  • ora-38702 : Cannot update flashback database log file header.
  • ora-19241 : XP0021 - cast to type string failed
  • ora-30396 : rewrite equivalence procedures require the COMPATIBLE parameter to be string or greater
  • ora-16050 : destination exceeded specified quota size
  • ora-30479 : Summary Advisor error string
  • ora-09822 : Translation of audit file name failed.
  • ora-01104 : number of control files (string) does not equal string
  • ora-29526 : created Java class string"string"
  • ora-19104 : invalid XQueryX: missing attribute string
  • ora-14183 : TABLESPACE DEFAULT can be specified only for Composite LOCAL index
  • ora-08175 : discrete transaction restriction violated (string)
  • ora-27472 : invalid metadata attribute string
  • ora-16719 : unable to query V$ARCHIVE_DEST fixed view
  • ora-13216 : failed to update spatial index
  • ora-09801 : Unable to get user ID from connection
  • ora-12353 : secondary stored object cannot reference remote object
  • ora-00018 : maximum number of sessions exceeded
  • ora-19863 : device block size string is larger than max allowed: string
  • ora-16032 : parameter string destination string cannot be translated
  • 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.