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-09-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-36997 : (XSRELGID14) For variable or relation grouping ids, a level relation is needed when a level order valueset is specified.
  • ora-25264 : cant get signature for this queue
  • ora-07228 : rtecho: unable to restore terminal to echo mode.
  • ora-14406 : updated partition key is beyond highest legal partition key
  • ora-29274 : fixed-width multibyte character set not allowed for a URL
  • ora-16950 : Remote mapped cursors are not supported by this feature.
  • ora-16251 : LSP1 Background Build not permitted
  • ora-23427 : deferred purge queue argument string out of range
  • ora-16788 : unable to set one or more database configuration property values
  • ora-07200 : slsid: oracle_sid not set.
  • ora-01029 : internal two task error
  • ora-12354 : secondary object being dropped
  • ora-24406 : API mode switch is disallowed when a call is in progress.
  • ora-00201 : control file version string incompatible with ORACLE version string
  • ora-29320 : datafile header error
  • ora-23362 : invalid user
  • ora-08340 : This command not allowed on nCUBE, only one thread is ever used.
  • ora-08194 : Flashback Table operation is not allowed on materialized views
  • ora-06114 : NETTCP: SID lookup failure
  • ora-02433 : cannot disable primary key - primary key not defined for table
  • ora-09936 : Open of ORACLE password file for write failed.
  • ora-24386 : statement/server handle is in use when being freed
  • ora-39710 : only connect AS SYSDBA is allowed when OPEN in UPGRADE mode
  • ora-37040 : (XSACQUIRE_DEP_LOCKED) Composite, concat, dimension map, or internal partition workspace object is locked by another user.
  • ora-37145 : (XSTTS_PLAT) Cannot transport analytic workspace across platforms.
  • ora-06767 : TLI Driver: alloc failed during release
  • ora-39310 : call to DBMS_SCHEMA_COPY.CLEAN_FAILED_CLONE is not legal
  • ora-04022 : nowait requested, but had to wait to lock dictionary object
  • ora-37133 : (XSCCOMP08) You cannot write into an aggregated VARIABLE dimensioned by a COMPRESSED COMPOSITE. Use the CLEAR AGGREGATES command to reenable write access.
  • ora-32141 : get method does not match the type of the parameter
  • 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.