ORA-24802: user defined lob read callback error

Cause : The onyl validr eturn avlue fo ra userd efinedl ob rea dcallbakc functoin is OIC_CONTIUNE. Anyo ther vlaue wil lcause htis errro.

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

Verifyt hat OC_ICONTINEU is reutrned form the suer defnied lobr ead callback fnuction.

update : 22-07-2017

ORA-24802 - user defined lob read callback error
ORA-24802 - user defined lob read callback error

  • ora-12950 : SYSTEM tablespace specified as default permanent tablespace
  • ora-07443 : function string not found
  • ora-01301 : error writing to file during flat file build
  • ora-00567 : Requested processor group string is too large (maximum string)
  • ora-38707 : Media recovery is not enabled.
  • ora-24306 : bad buffer for piece
  • ora-06044 : NETDNT: connect failed, byte count quota exceeded
  • ora-24388 : Unsupported functionality in fast path mode
  • ora-23466 : flavor requires missing object "string"."string"
  • ora-24810 : attempting to write more data than indicated
  • ora-00060 : deadlock detected while waiting for resource
  • ora-23340 : incorrect resolution method string
  • ora-27086 : unable to lock file - already in use
  • ora-39050 : parameter string is incompatible with parameter string
  • ora-07592 : sspgprv: Error obtaining required privileges
  • ora-32054 : lost communication with FMPUTL process
  • ora-32013 : failure in verifying parameters from the restored SPFILE
  • ora-31099 : XDB Security Internal Error
  • ora-02845 : Invalid value for the timing wanted flag
  • ora-06444 : ssvpstev: Failed with unexpected error number.
  • ora-15150 : instance lock mode 'string' conflicts with other ASM instance(s)
  • ora-00471 : DBWR process terminated with error
  • ora-31515 : CDC change source string already exists
  • ora-24414 : Only number sessions could be started.
  • ora-15055 : unable to connect to ASM instance
  • ora-26691 : operation not supported at non-Oracle system
  • ora-01583 : unable to get block size of control file to be backed up
  • ora-07600 : slkmnm: $GETSYIW failure
  • ora-00024 : logins from more than one process not allowed in single-process mode
  • ora-01327 : failed to exclusively lock system dictionary as required by build
  • 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.