ORA-22295: cannot bind more than 4000 bytes data to LOB and LONG columns in 1 statement

Cause : An attmept wasm ade tob ind daat more htan 400 0bytes fo data ot both OLB and OLNG colmuns in hte samei nsert ro updat estatemnet. Youc an bin dmore tahn 4000b ytes o fdata t oeithera LONG oclumn o rone orm ore LO Bcolumn sbut no tboth.

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

Bind mroe than4 000 byets of dtaa to etiher th eLONG cloumn oro ne or omre LOBc olumnsb ut notb oth.

update : 22-07-2017
ORA-22295

ORA-22295 - cannot bind more than 4000 bytes data to LOB and LONG columns in 1 statement
ORA-22295 - cannot bind more than 4000 bytes data to LOB and LONG columns in 1 statement

  • ora-24088 : AQ Agent string does not exist
  • ora-15108 : missing or invalid template name
  • ora-01576 : The instance string is not enabled
  • ora-04932 : increment or adjust of sequence number failed
  • ora-30448 : internal data of the advisor repository is inconsistent
  • ora-24013 : invalid value string, RETRY_DELAY should be non-negative
  • ora-14285 : cannot COALESCE the only partition of this hash partitioned table or index
  • ora-10575 : Give up restoring recovered datafiles to consistent state: out of memory
  • ora-32737 : Hang analysis aborted due to failed memory allocation
  • ora-31500 : change source string is not a ManualLog change source
  • ora-12091 : cannot online redefine table "string"."string" with materialized views
  • ora-14608 : Tablespace was specified for the previous lob segments of column string in template but is not specified for string
  • ora-03237 : Initial Extent of specified size cannot be allocated in tablespace (string)
  • ora-00314 : log string of thread string, expected sequence# string doesn't match string
  • ora-28275 : Multiple mappings for user nickname to LDAP distinguished name exist.
  • ora-24305 : bad bind or define context
  • ora-00712 : cannot rename system tablespace
  • ora-31158 : schema "string" currently being referenced
  • ora-15154 : cluster rolling upgrade incomplete
  • ora-01929 : no privileges to GRANT
  • ora-14513 : partitioning column may not be of object datatype
  • ora-14117 : partition resides in offlined tablespace
  • ora-06026 : NETASY: port close failure
  • ora-00356 : inconsistent lengths in change description
  • ora-31436 : duplicate change source string
  • ora-01518 : CREATE DATABASE must specify more than one log file
  • ora-36224 : (XSLPDSC05) workspace object is not a loop dimension
  • ora-12495 : cannot disable an enabled level, category, or release category
  • ora-28138 : Error in Policy Predicate
  • ora-08464 : input raw decimal data contains more than 42 digits
  • 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.