ORA-24808: streaming of lob data is not allowed when using lob buffering

Cause : Attempted to stream lob data via the polling mode or a callback when lob buffering was enabled for the input lob locator.

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

Lob buffering is useful when reading/writing small amounts of lob data so streaming should not be necessary. Rewrite the OCILobRead/OCILobWrite call so that it does not use streaming. If streaming of data is required, lob buffering should not be used. In this case, flush buffers associated with the input lob locator as necessary, disable buffering on the input lob locator and reissue the OCILobRead/OCILobWrite call.

update : 26-04-2017
ORA-24808

ORA-24808 - streaming of lob data is not allowed when using lob buffering
ORA-24808 - streaming of lob data is not allowed when using lob buffering

  • ora-31405 : cannot make changes while change set string is advancing
  • ora-32801 : invalid value string for string
  • ora-09771 : osnmwrtbrkmsg: bad return code from msg_send.
  • ora-07470 : snclget: cannot get cluster number.
  • ora-15058 : disk 'string' belongs to an incompatible diskgroup
  • ora-31214 : DBMS_LDAP: PL/SQL - Invalid LDAP mod type.
  • ora-07624 : smsdes: $DGBLSC failure
  • ora-28140 : Invalid column specified
  • ora-31071 : Invalid database username or GUID string
  • ora-24408 : could not generate unique server group name
  • ora-29260 : network error: string
  • ora-31675 : worker process interrupt for unexpected death of master process
  • ora-32633 : MODEL subquery FOR cell index returns too many rows
  • ora-19589 : %s is not a snapshot or backup control file
  • ora-24376 : cannot register/get user callback for non-environment handle
  • ora-19957 : database should have no datafiles in unknown state
  • ora-31490 : could not attach to LogMiner session
  • ora-36908 : (XSAGDNGL46) In AGGMAP workspace object, MODEL workspace object has the repeating dimension with the previous model.
  • ora-22880 : invalid REF
  • ora-06137 : NETTCP: error during connection handshake
  • ora-38405 : quotes not allowed in the attribute set name
  • ora-13789 : invalid process action
  • ora-25191 : cannot reference overflow table of an index-organized table
  • ora-14503 : only one partition name can be specified
  • ora-02808 : Allocation of memory of open files array failed.
  • ora-13429 : invalid xCoefficients or yCoefficients parameter(s)
  • ora-39061 : import mode string conflicts with export mode string
  • ora-07208 : sfwfb: failed to flush dirty buffers to disk.
  • ora-15166 : cluster in rolling downgrade from version [string] to [string]
  • ora-14102 : only one LOGGING or NOLOGGING clause may be specified
  • 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.