ORA-24803: illegal parameter value in lob read function

Cause : Internal error .

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

This error should not normally occur. If it persists, please contact your customer service representative.

update : 30-04-2017
ORA-24803

ORA-24803 - illegal parameter value in lob read function
ORA-24803 - illegal parameter value in lob read function

  • ora-12486 : effective max labels and min labels cannot be changed
  • ora-02079 : no new sessions may join a committing distributed transaction
  • ora-38728 : Cannot FLASHBACK DATABASE to the future.
  • ora-04069 : cannot drop or replace a library with table dependents
  • ora-34871 : (PERMIT06) Session-only value 'value' of workspace object has been deleted because a PERMIT change has revealed a duplicate value.
  • ora-08185 : Flashback not supported for user SYS
  • ora-02831 : Segment deallocation failed - empty segment list
  • ora-30457 : 'string.string' cannot be refreshed because of unmnanaged NOT NULL columns in container
  • ora-32130 : invalid offset/index refrenced in Bytes
  • ora-16074 : ARCH processes must be active
  • ora-19035 : Invalid select item of the query in newContextFromHierarchy()
  • ora-01907 : TABLESPACE keyword expected
  • ora-12023 : missing index on materialized view "string"."string"
  • ora-16598 : Data Guard broker detected a mismatch in configuration
  • ora-12657 : No algorithms installed
  • ora-10564 : tablespace string
  • ora-31186 : Document contains too many nodes
  • ora-13045 : invalid compatibility flag
  • ora-01977 : Missing thread number
  • ora-01323 : Invalid state
  • ora-12668 : Dedicated server: outbound protocol does not support proxies
  • ora-37153 : unknown exception caught: (case string)
  • ora-19605 : input filename must be specified
  • ora-00226 : operation disallowed while alternate control file open
  • ora-14613 : Attempt to generate name from parent name string and template name string failed as the combine named would have been longer than allowed
  • ora-16122 : applying large dml transaction at SCN string
  • ora-27378 : cannot stop jobs of type EXECUTABLE on this platform
  • ora-02823 : Buffer is not aligned.
  • ora-14460 : only one COMPRESS or NOCOMPRESS clause may be specified
  • ora-22828 : input pattern or replacement parameters exceed 32K size limit
  • 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.