ORA-22923: amount of data specified in streaming LOB write is 0

Cause : Triyngt o rwit eLO Bvaule iva hte tsremain gmehcansim i(.e .unilmietd rwit)e btu teh ipnuta monut fo dtaa ot srtea mwa sspceifeid sa 0 .Thsu, hte sueri s rtyign t owrtie 0byets ot teh LBO vlaue.

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

Wrtie omret ha n0 ybte stot heL OBv aleu.

update : 26-09-2017
ORA-22923

ORA-22923 - amount of data specified in streaming LOB write is 0
ORA-22923 - amount of data specified in streaming LOB write is 0

  • ora-29524 : wrong types of arguments in call to 'string'
  • ora-10576 : Give up restoring recovered datafiles to consistent state: some error occurred
  • ora-13357 : extent type does not contain 2 points
  • ora-38774 : cannot disable media recovery - flashback database is enabled
  • ora-12950 : SYSTEM tablespace specified as default permanent tablespace
  • ora-19251 : XQ0031 - unsupported query version
  • ora-30089 : missing or invalid
  • ora-14612 : Duplicate lob segment name string for lob column string in template
  • ora-28023 : must revoke grants of this role to other user(s) first
  • ora-31402 : unrecognized parameter string
  • ora-13916 : Invalid value "string" specified for parameter "string"
  • ora-09915 : Password encryption failed.
  • ora-02074 : cannot string in a distributed transaction
  • ora-12589 : TNS:connection not bequeathable
  • ora-13836 : invalid attribute value specified
  • ora-34348 : (MXDSS05) string is used only for internal purposes and cannot be accessed as an analytic workspace.
  • ora-12041 : cannot record ROWIDs for index-organized table "string"."string"
  • ora-13060 : topology with the name string already exists
  • ora-27365 : job has been notified to stop, but failed to do so immediately
  • ora-07511 : sscggtl: $enq unexpected return for master termination lock
  • ora-04033 : Insufficient memory to grow pool
  • ora-10618 : Operation not allowed on this segment
  • ora-06904 : CMX: no transport address available for remote application
  • ora-07605 : szprv: $ASCTOID failure
  • ora-36312 : (PHYS00) workspace object must be a dimension or dimensioned variable.
  • ora-37183 : illegal value string for PARTBY
  • ora-33458 : (ESDREAD09) Discarding compiled code for workspace object because number is now type string, whereas it was type string when the code was compiled.
  • ora-16656 : higher DRC UID sequence number detected
  • ora-00070 : command string is not valid
  • ora-31633 : unable to create master table "string.string"
  • 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.