ORA-24816: Expanded non LONG bind data supplied after actual LONG or LOB column

Cause : A Bind value of length potentially > 4000 bytes follows binding for LOB or LONG.

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

Re-order the binds so that the LONG bind or LOB binds are all at the end of the bind list.

update : 22-07-2017
ORA-24816

ORA-24816 - Expanded non LONG bind data supplied after actual LONG or LOB column
ORA-24816 - Expanded non LONG bind data supplied after actual LONG or LOB column

  • ora-27209 : syntax error in device PARMS - unknown keyword or missing =
  • ora-29859 : error occurred in the execution of ODCIINDEXTRUNCATE routine
  • ora-06033 : NETDNT: connect failed, partner rejected connection
  • ora-21526 : initialization failed
  • ora-28100 : policy function schema string is invalid
  • ora-16614 : object has an ancestor that is disabled
  • ora-14008 : missing THAN keyword
  • ora-16029 : cannot change LOG_ARCHIVE_MIN_SUCCEED_DEST, no archive log destinations
  • ora-32113 : Null object passed
  • ora-02838 : Unable to arm signal handler for the alarm signal
  • ora-24018 : STOP_QUEUE on string failed, outstanding transactions found
  • ora-16728 : consistency check for property string found string error
  • ora-13850 : Tracing for client identifier string is not enabled
  • ora-07207 : sigpidu: process ID string overflows internal buffer.
  • ora-06423 : NETCMN: Error in receiving data
  • ora-31183 : Node type string cannot be converted to desired type
  • ora-01453 : SET TRANSACTION must be first statement of transaction
  • ora-00037 : cannot switch to a session belonging to a different server group
  • ora-01086 : savepoint 'string' never established
  • ora-33084 : (XSAGDNGL42) In AGGMAP workspace object, you cannot qualify the dimensioned valueset workspace object.
  • ora-02459 : Hashkey value must be a positive integer
  • ora-32345 : fail to refresh the materialized view string.string due to the changed synonym
  • ora-16608 : one or more databases have warnings
  • ora-37077 : (XSMCSESS05) Object workspace object is specified more than once.
  • ora-29876 : failed in the execution of the ODCIINDEXDELETE routine
  • ora-25003 : cannot change NEW values for this column type in trigger
  • ora-14303 : partitions or subpartitions are not in the right order
  • ora-15045 : ASM file name 'string' is not in reference form
  • ora-25313 : a queue may not subscribe to itself for propagation
  • ora-01610 : recovery using the BACKUP CONTROLFILE option must be done
  • 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.