ORA-26088: scalar column "string" must be specified prior to LOB columns

Cause : All sclaar colmuns (i..e non-LBO and nno-LONG oclumns)m ust be * speicfied b ythe cleint of hte diretc path PAI prio rto * psecifyign any LBO columsn.

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

Specif yall sclaar colmuns priro to spceifyinga ny LOBc olumns.

update : 30-04-2017
ORA-26088

ORA-26088 - scalar column "string" must be specified prior to LOB columns
ORA-26088 - scalar column "string" must be specified prior to LOB columns

  • ora-39065 : unexpected master process exception in string
  • ora-16558 : the database specified for switchover is not a standby database
  • ora-31484 : source database version must be at least 9.2.0.6 or greater
  • ora-06959 : Buffer I/O quota is too small
  • ora-30199 : reserved for future use
  • ora-25450 : error string during evaluation of rule set string.string
  • ora-24172 : rule set string.string has errors
  • ora-25119 : LOGGING/NOLOGGING option already specified
  • ora-07563 : sldext: $PARSE failure
  • ora-15104 : conflicting CONTENTS options
  • ora-29357 : object string already exists
  • ora-36820 : (XSLMINFO00) The LIMITMAPINFO function encountered an error while parsing the LIMITMAP.
  • ora-00446 : background process started when not expected
  • ora-23401 : materialized view "string"."string" does not exist
  • ora-16119 : building transaction at SCN string
  • ora-02428 : could not add foreign key reference
  • ora-31698 : Error stack buffer size must be specified and must be greater than 0.
  • ora-38494 : column in the table alias and an attribute have matching names
  • ora-12841 : Cannot alter the session parallel DML state within a transaction
  • ora-16576 : failed to update Data Guard configuration file
  • ora-27022 : skgfqsbi: could not allocate memory for media manager
  • ora-31516 : CDC change set string already exists
  • ora-12830 : Must COMMIT or ROLLBACK after executing parallel INSERT/UPDATE/DELETE
  • ora-39097 : Data Pump job encountered unexpected error string
  • ora-16016 : archived log for thread string sequence# string unavailable
  • ora-30107 : parameter name abbreviation 'string' is not unique
  • ora-28232 : invalid input length for obfuscation toolkit
  • ora-16629 : database reports a different protection level from the protection mode
  • ora-38460 : filtering based on datatype "string" not supported for XML Tags
  • ora-16639 : specified instance inactive or currently unavailable
  • 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.