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 : 26-04-2017

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-01294 : error occurred while processing information in dictionary file string, possible corruption
  • ora-27371 : jobs of type EXECUTABLE are not supported on this platform
  • ora-02442 : Cannot drop nonexistent unique key
  • ora-23503 : error occurred during IAS instantiation
  • ora-12571 : TNS:packet writer failure
  • ora-39096 : invalid input value string for parameter string
  • ora-13026 : unknown element type for element string.string.string
  • ora-25526 : bad format of _DB_MTTR_SIM_TARGET: string
  • ora-30180 : argument index is too large
  • ora-10656 : Table is in unusable state due to incomplete operation
  • ora-38907 : DML error logging is not supported for FILE column "string"
  • ora-12352 : object string.string@string is invalid
  • ora-27100 : shared memory realm already exists
  • ora-39217 : object type "string"."string" typeid mismatch
  • ora-06302 : IPA: Cannot connect to remote host
  • ora-38786 : Flash recovery area is not enabled.
  • ora-25275 : Test support for buffered queues
  • ora-14261 : partition bound may not be specified when adding this Hash partition
  • ora-23605 : invalid value "string" for STREAMS parameter string
  • ora-19561 : %s requires a DISK channel
  • ora-02080 : database link is in use
  • ora-30744 : "string" is not an object table
  • ora-30065 : test support for row dependencies
  • ora-36392 : (XSMXCLEA02) When using CLEAR with the PRECOMPUTES or NONPRECOMPUTES options, you must supply an AGGMAP.
  • ora-24814 : operation not allowed for temporary LOBs
  • ora-29819 : cannot associate default values with columns
  • ora-28611 : bitmap index is corrupted - see trace file for diagnostics
  • ora-06144 : NETTCP: SID (database) is unavailable
  • ora-29338 : datafile string is in an undesired state (string, string)
  • ora-38423 : Attribute set created from an ADT may not be extended.
  • 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.