ORA-26089: LONG column "string" must be specified last

Cause : A cleint o fthe idrectp ath PAI spceifie da LOGN colmun tob e *loadde, bu tthe OLNG cloumn aws no tthe alst cloumn ot be * speicfied.

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

Specfiy th eLONGc olum nlast.

update : 28-06-2017

ORA-26089 - LONG column "string" must be specified last
ORA-26089 - LONG column "string" must be specified last

  • ora-00825 : cannot set db_block_buffers if sga_target set
  • ora-16571 : Data Guard configuration file creation failure
  • ora-39752 : redundant column in partitioning and join columns is not allowed
  • ora-22880 : invalid REF
  • ora-08459 : invalid format parameter length
  • ora-12424 : length exceeds binary label size
  • ora-23302 : application raised communication failure during deferred RPC
  • ora-34181 : (MXCHGDCL21) workspace object is not a partitioned VARIABLE.
  • ora-25957 : join index where clause cannot contain cycles
  • ora-30729 : maximum number of columns exceeded
  • ora-36342 : (SNSYN200) The format of the CLEAR command is: CLEAR [ ALL | STATUS ] [ AGGREGATES | CHANGES | PRECOMPUTES | NONPRECOMPUTES | CACHE ] FROM var1 [var2, var3...] [USING aggmap]
  • ora-08261 : ora_addr: cannot find name in nameserver
  • ora-16099 : internal error ORA-00600 occurred at standby database
  • ora-22928 : invalid privilege on directories
  • ora-01545 : rollback segment 'string' specified not available
  • ora-19806 : cannot make duplex backups in recovery area
  • ora-13149 : failed to generate next sequence number for spatial table string
  • ora-40281 : invalid model name
  • ora-13625 : %s is an invalid advisor object type.
  • ora-14084 : you may specify TABLESPACE DEFAULT only for a LOCAL index
  • ora-00401 : the value for parameter string is not supported by this release
  • ora-30067 : Internal Event to turn on nested debugging info
  • ora-02776 : Value for request done signal exceeds maximum
  • ora-07237 : slemcl: invalid file handle, seals do not match.
  • ora-23430 : argument "string" cannot be NULL or empty string
  • ora-31472 : Importing Change Data Capture version string.string is too new
  • ora-16573 : attempt to change configuration file for an enabled broker configuration
  • ora-13339 : LRS polygon clipping across multiple rings
  • ora-27399 : job type EXECUTABLE requires the CREATE EXTERNAL JOB privilege
  • ora-31417 : column list contains control column string
  • 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.