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-05-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-31697 : aborting operation at process order number string
  • ora-08311 : sllfop: bad value for maxrecsize
  • ora-30119 : unable to obtain a valid value for 'string'
  • ora-00349 : failure obtaining block size for 'string'
  • ora-01511 : error in renaming log/data files
  • ora-15007 : name is already used by an existing template
  • ora-13506 : operation failed due to invalid snapshot range (string, string)
  • ora-19615 : some files not found in backup set
  • ora-24169 : rule condition has unrecognized variables
  • ora-15069 : ASM file 'string' not accessible; timed out waiting for lock
  • ora-01610 : recovery using the BACKUP CONTROLFILE option must be done
  • ora-07482 : snlmini: cannot create lock manager instance.
  • ora-23293 : Cannot rename a column which is part of a join index
  • ora-37026 : (XSMLTRESYNC01) Object workspace object cannot be resynced without dimension workspace object.
  • ora-37158 : Bad clob or varray IN-args: (case string)
  • ora-36200 : (XSAGGR34) AGGREGATE operator string requires a WEIGHTBY clause, but ARGS variable workspace object did not specify one.
  • ora-16091 : dependent archive log destination already archived
  • ora-12993 : tablespace 'string' is offline, cannot drop column
  • ora-13330 : invalid MASK
  • ora-00063 : maximum number of log files exceeded string
  • ora-19900 : RESETLOGS must be specified after recovery to new incarnation
  • ora-13505 : SYSAUX tablespace can not be made read only
  • ora-27071 : unable to seek to desired position in file
  • ora-09881 : sstasfre/sstasdel: shmdt error, unable to detach tas read page
  • ora-12421 : different size binary labels
  • ora-32844 : exceeded maximum number of string values
  • ora-30479 : Summary Advisor error string
  • ora-16148 : user requested expiration of managed recovery operation
  • ora-26046 : REF column string expects scoped table name string; user passed in string.
  • ora-06143 : NETTCP: maximum connections exceeded
  • 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.