ORA-22835: Buffer too small for CLOB to CHAR or BLOB to RAW conversion (actual: string, maximum: string)

Cause : An attempt was made to convert CLOB to CHAR or BLOB to RAW, where the LOB size was bigger than the buffer limit for CHAR and RAW types. Note that widths are reported in characters if character length semantics are in effect for the column, otherwise widths are reported in bytes.

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

Do one of the following: 1. Make the LOB smaller before performing the conversion, for example, by using SUBSTR on CLOB 2. Use DBMS_LOB.SUBSTR to convert CLOB to CHAR or BLOB to RAW.

update : 30-04-2017
ORA-22835

ORA-22835 - Buffer too small for CLOB to CHAR or BLOB to RAW conversion (actual: string, maximum: string)
ORA-22835 - Buffer too small for CLOB to CHAR or BLOB to RAW conversion (actual: string, maximum: string)

  • ora-12524 : TNS:listener could not resolve HANDLER_NAME given in connect descriptor
  • ora-04940 : unsupported optimization of Oracle binary, check alert log for more info
  • ora-07600 : slkmnm: $GETSYIW failure
  • ora-23445 : missing template site
  • ora-15162 : cluster in rolling downgrade
  • ora-30159 : OCIFileOpen: Cannot create the file or cannot open in the requested mode
  • ora-07485 : scg_get_inst: cannot open instance number lock.
  • ora-12612 : TNS:connection is busy
  • ora-39041 : Filter "string" either identifies all object types or no object types.
  • ora-02717 : osnpfs: incorrect number of bytes written
  • ora-12723 : regular expression too complex
  • ora-07282 : sksaprd: string overflow.
  • ora-07393 : unable to delete text file
  • ora-28110 : policy function or package string.string has error
  • ora-31014 : Attempted to delete the root container
  • ora-02145 : missing STORAGE option
  • ora-27012 : skgfrd: read from file failed
  • ora-13016 : specified topology [string] is invalid
  • ora-26714 : User error encountered while applying
  • ora-32501 : Writing SGA to file failed
  • ora-29340 : export file appears to be corrupted: [string] [string] [string]
  • ora-36669 : (XSDPART07) string is not a legal LIST partition.
  • ora-23420 : interval must evaluate to a time in the future
  • ora-31605 : the following was returned from string in routine string: LPX-number: string
  • ora-09949 : Unable to get client operating system privileges
  • ora-15123 : ASM file name 'string' contains an invalid incarnation number
  • ora-31636 : session is already attached to job string for user string
  • ora-01866 : the datetime class is invalid
  • ora-32700 : error occurred in DIAG Group Service
  • ora-01319 : Invalid Logminer session attribute
  • 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.