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 : 18-08-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-24276 : function 'string' output 'string' maximum value exceeded
  • ora-29289 : directory access denied
  • ora-09319 : slgtd: unable to obtain the current date and time
  • ora-25150 : ALTERING of extent parameters not permitted
  • ora-30483 : window functions are not allowed here
  • ora-01671 : control file is a backup, cannot make a standby control file
  • ora-01311 : Illegal invocation of the mine_value function
  • ora-39317 : call to DBMS_SCHEMA_COPY.VALIDATION_CHECK is not legal
  • ora-09976 : skxfqdini: Error Creating Port
  • ora-25305 : enqueue failed, expiration must be zero for queue string.string
  • ora-31002 : Path name string is not a container
  • ora-02262 : ORA-string occurs while type-checking column default value expression
  • ora-12606 : TNS: Application timeout occurred
  • ora-14278 : column type or size mismatch in EXCHANGE SUBPARTITION
  • ora-39126 : Worker unexpected fatal error in string [string] string
  • ora-30116 : syntax error at 'string' following 'string'
  • ora-29859 : error occurred in the execution of ODCIINDEXTRUNCATE routine
  • ora-25406 : could not generate a connect address
  • ora-16063 : remote archival is enabled by another instance
  • ora-25278 : grantee name cannot be NULL
  • ora-38856 : cannot mark instance string (redo thread string) as enabled
  • ora-01127 : database name 'string' exceeds size limit of string characters
  • ora-09878 : sstascre/sstasat: shmat error, unable to attach tas write page
  • ora-31496 : must use DBMS_CDC_PUBLISH.DROP_CHANGE_TABLE to drop change tables
  • ora-32742 : Hang analysis initialize failed
  • ora-19777 : ASM file string cannot be proxy backed up.
  • ora-39149 : cannot link privileged user to non-privileged user
  • ora-24160 : name string already exists in the name value pair list
  • ora-14621 : cannot add subpartition when DEFAULT subpartition exists
  • ora-38405 : quotes not allowed in the attribute set name
  • 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.