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 : 18-08-2017

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-32301 : object-relational materialized views must be primary key based
  • ora-01984 : invalid auditing option for procedures/packages/functions
  • ora-32837 : invalid configuration state string
  • ora-33462 : (ESDREAD10A) Discarding compiled code for workspace object because object number is not in analytic workspace string.
  • ora-00274 : illegal recovery option string
  • ora-01183 : cannot mount database in SHARED mode
  • ora-36976 : (XSRELGID00) The format of the GROUPINGID command is: GROUPINGID [relation1] INTO {variable | relation2 | surrogate} [USING levelrelation] [INHIERARCHY {inhvariable | valueset}] [LEVELORDER levelordervs] The source relation can be omitted only when using both surrogate gid and level order valueset.
  • ora-00474 : SMON process terminated with error
  • ora-12040 : master rollback segment option not support by master site string
  • ora-00233 : copy control file is corrupt or unreadable
  • ora-13411 : subset results in null data set
  • ora-13220 : failed to compare tile with the geometry
  • ora-15201 : disk string contains a valid RDBMS file
  • ora-19616 : output filename must be specified if database not mounted
  • ora-31515 : CDC change source string already exists
  • ora-07632 : smsrcx: $DELTVA failure
  • ora-19033 : schema specified in the XML document does not match the schema parameter
  • ora-29901 : function underlying operator binding does not exist
  • ora-06737 : TLI Driver: connection failed
  • ora-21707 : pin duration is longer than allocation duration
  • ora-24769 : cannot forget an active transaction
  • ora-19752 : block change tracking is already enabled
  • ora-12854 : Parallel query is not supported on temporary LOBs
  • ora-14028 : missing AT or VALUES keyword
  • ora-33413 : (EIFMAKEF01) You cannot export compressed composite workspace object because one of its bases has limited status or a PERMIT READ restriction.
  • ora-14011 : names assigned to resulting partitions must be distinct
  • ora-01645 : previous attempt to make read write is half complete
  • ora-16140 : standby online logs have not been recovered
  • ora-22806 : not an object or REF
  • ora-32408 : materialized view log on "string"."string" already has new values
  • 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.