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 : 23-07-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-31116 : Tablespace not specified correctly
  • ora-08005 : specified row does not exist
  • ora-03136 : inbound connection timed out
  • ora-30398 : illegal JOIN KEY clause
  • ora-29348 : You must specify the datafiles to be plugged in
  • ora-12647 : Authentication required
  • ora-02779 : Stat failed on core dump directory
  • ora-06777 : TLI Driver: error reading parms
  • ora-38733 : Physical size string less than needed string.
  • ora-27472 : invalid metadata attribute string
  • ora-39077 : unable to subscribe agent string to queue "string"
  • ora-06817 : TLI Driver: could not read the Novell network address
  • ora-22868 : table with LOBs contains segments in different tablespaces
  • ora-04021 : timeout occurred while waiting to lock object stringstringstringstringstring
  • ora-31040 : Property string: XML type (string) not compatible with internal memory type (string)
  • ora-25295 : Subscriber is not allowed to dequeue buffered messages
  • ora-12224 : TNS:no listener
  • ora-16080 : invalid LogMiner session string for APPLY
  • ora-23505 : Object "string"."string" is missing.
  • ora-17618 : Unable to update block 0 to version 10 format
  • ora-28182 : cannot acquire Kerberos service ticket for client
  • ora-01880 : the fractional seconds must be between 0 and 999999999
  • ora-01230 : cannot make read only - file string is offline
  • ora-06123 : NETTCP: cannot set KEEPALIVE
  • ora-30979 : Partitioned XML Index not yet supported.
  • ora-12913 : Cannot create dictionary managed tablespace
  • ora-12736 : Instant Client Light: unsupported server national character set string
  • ora-19285 : FODC0002 - error retrieving resource
  • ora-12552 : TNS:operation was interrupted
  • ora-12641 : Authentication service failed to initialize
  • 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.