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 : 23-09-2017

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-38408 : The ADT "string" does not exist in the current schema.
  • ora-27089 : unable to release advisory lock
  • ora-16524 : unsupported operation
  • ora-31401 : change source string is not an existing change source
  • ora-31452 : invalid value string for parameter, expecting: Y or N
  • ora-02229 : invalid SIZE option value
  • ora-39042 : invalid transform name string
  • ora-01526 : error in opening file 'string'
  • ora-39763 : stream must be completely loaded before it is reset
  • ora-02778 : Name given for the log directory is invalid
  • ora-29929 : missing SCAN Keyword
  • ora-14109 : partition-extended object names may only be used with tables
  • ora-34276 : (MXDCL33) (Precision, Scale) arguments can only be used with a NUMBER variable or dimension.
  • ora-36641 : (XSDUNION20) The concat dimension must be defined as UNIQUE because base dimension workspace object contains custom member values.
  • ora-31155 : attribute string not in XDB namespace
  • ora-01878 : specified field not found in datetime or interval
  • ora-00061 : another instance has a different DML_LOCKS setting
  • ora-14074 : partition bound must collate higher than that of the last partition
  • ora-02050 : transaction string rolled back, some remote DBs may be in-doubt
  • ora-07617 : $FORMAT_CLASS failed translating the binary label to a string
  • ora-16257 : Switchover initiated stop apply successfully completed
  • ora-27087 : unable to get share lock - file not readable
  • ora-36961 : Oracle OLAP is not available.
  • ora-28300 : No permission to read user entry in LDAP directory service.
  • ora-02240 : invalid value for OBJNO or TABNO
  • ora-31442 : operation timed out while acquiring lock on string
  • ora-31475 : redo log catalog contains no metadata for the source table
  • ora-30107 : parameter name abbreviation 'string' is not unique
  • ora-36999 : (XSRELGID16) OBJECT workspace object is not a surrogate dimension, a source relation must be specified when creating any non-surrogate grouping id.
  • ora-15034 : disk 'string' does not require the FORCE option
  • 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.