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-09-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-29296 : invalid encoded string
  • ora-39503 : failed to notify CRS of a Startup/Shutdown event [string] (ignored)
  • ora-01873 : the leading precision of the interval is too small
  • ora-19755 : could not open change tracking file
  • ora-00706 : error changing format of file 'string'
  • ora-39764 : specified stream is not in the specified direct path context
  • ora-09938 : Save of signal handlers failed.
  • ora-15182 : ASMLIB [string] version mismatch, ORACLE version [string]
  • ora-22614 : error while construction the collection in the image
  • ora-36908 : (XSAGDNGL46) In AGGMAP workspace object, MODEL workspace object has the repeating dimension with the previous model.
  • ora-25350 : maximum number of concurrent transaction branches exceeded
  • ora-12951 : Attempt to change default permanent tablespace to temporary
  • ora-00323 : Current log of thread string not useable and all others need archiving
  • ora-13458 : GeoRaster metadata SRS error
  • ora-01920 : user name 'string' conflicts with another user or role name
  • ora-13217 : invalid parameters supplied in ALTER INDEX statement
  • ora-12602 : TNS: Connection Pooling limit reached
  • ora-09857 : smprset: vm_protect error while protecting pga.
  • ora-32502 : Cannot execute command. Flash Freeze is not in effect
  • ora-29885 : domain index is defined on the column to be modified
  • ora-39095 : Dump file space has been exhausted: Unable to allocate string bytes
  • ora-08462 : raw buffer contains invalid decimal data
  • ora-12583 : TNS:no reader
  • ora-16707 : the value of the property string is invalid, valid values are string
  • ora-30064 : Test support for two phase read only optimization
  • ora-01524 : cannot create data file as 'string' - file already part of database
  • ora-25250 : Cannot specify a remote recipient for the message
  • ora-22999 : CLOB or NCLOB data may have been corrupted
  • ora-02716 : osnpgetdatmsg: message from host had incorrect message type
  • ora-00712 : cannot rename system tablespace
  • 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.