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 : 24-05-2017
ORA-26089

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

  • ora-26507 : null master connection
  • ora-13601 : The specified Advisor string does not exist.
  • ora-36968 : (XSRELTBL11) workspace object must be a relation.
  • ora-00096 : invalid value string for parameter string, must be from among string
  • ora-09718 : osnsui: cannot set up user interrupt handler.
  • ora-16251 : LSP1 Background Build not permitted
  • ora-36980 : (XSRELGID02) Variable workspace object must have a numeric data type.
  • ora-30354 : Query rewrite not allowed on SYS relations
  • ora-14086 : a partitioned index may not be rebuilt as a whole
  • ora-23471 : template not authorized for user
  • ora-13702 : Snapshot IDs specified by the range [string, string] are equal.
  • ora-22328 : object "string"."string" has errors. string
  • ora-37007 : (AWLISTALL05) number writer
  • ora-19906 : recovery target incarnation changed during recovery
  • ora-16080 : invalid LogMiner session string for APPLY
  • ora-31642 : the following SQL statement fails: string
  • ora-15177 : cannot operate on system aliases
  • ora-31191 : Resource string is already checked out
  • ora-19333 : Invalid flags for the CREATE_DBURI operator
  • ora-32117 : Source LOB is null
  • ora-12069 : invalid object for offline instantiation
  • ora-01341 : LogMiner out-of-memory
  • ora-02049 : timeout: distributed transaction waiting for lock
  • ora-02269 : key column cannot be of LONG datatype
  • ora-13616 : The current user string has not been granted the ADVISOR privilege.
  • ora-27150 : attempt to notify process of pending oradebug call failed
  • ora-16113 : applying change to table or sequence string
  • ora-22855 : optional name for LOB storage segment incorrectly specified
  • ora-10634 : Segment is already being shrunk
  • ora-01637 : rollback segment 'string' is being used by another instance (#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.