ORA-14302: only one list of added-LOB-storage-clauses can be specified in a statement

Cause : While parsing an ALTER TABLE ADD COLUMN statement, one list of added-LOB-storage-clauses was parsed when another list of added-LOB-storage-clauses was encountered. There cannot be more than one list of added-LOB-storage-clauses in a statement; all added-LOB-storage-clauses must be combined into one list.

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

Combine all of the lists of added-LOB-storage-clauses into one list and retry the statement.

update : 20-08-2017
ORA-14302

ORA-14302 - only one list of added-LOB-storage-clauses can be specified in a statement
ORA-14302 - only one list of added-LOB-storage-clauses can be specified in a statement

  • ora-27479 : Cannot string "string.string" because other objects depend on it
  • ora-18008 : cannot find OUTLN schema
  • ora-30737 : cannot create subtable of a type which is not a subtype of the type of the supertable
  • ora-14269 : cannot exchange partition other than a Range or Hash partition
  • ora-26524 : nls subsystem initialization failure for product=string, facility=string
  • ora-31512 : name cannot contain double quotation marks
  • ora-26023 : index string.string partition string was made unusable due to:
  • ora-07230 : slemcr: fopen error, unable to open error file.
  • ora-06735 : TLI Driver: client failed to close error conn
  • ora-12488 : maximum label does not dominate minimum label
  • ora-23438 : missing refresh group template
  • ora-12016 : materialized view does not include all primary key columns
  • ora-36178 : (XSAGGR01) To be used with AGGREGATE, AGGMAP workspace object must be declared with the AGGMAP command.
  • ora-02357 : no valid dump files
  • ora-06808 : TLI Driver: could not link IPX and ethernet streams
  • ora-27508 : IPC error sending a message
  • ora-01513 : invalid current time returned by operating system
  • ora-01592 : error converting Version 7 rollback segment (string) to Oracle 8 format
  • ora-16719 : unable to query V$ARCHIVE_DEST fixed view
  • ora-12335 : database (link name string) is not open
  • ora-01553 : MAXEXTENTS must be no smaller than the string extents currently allocated
  • ora-31618 : dump file size too small
  • ora-16958 : DML statements running parallel are not supported for test execute.
  • ora-00126 : connection refused; invalid duplicity
  • ora-10587 : Invalid count for ALLOW n CORRUPTION option
  • ora-36912 : (XSAGDNGL48) In AGGMAP workspace object, MODEL workspace object cannot be simultaneous.
  • ora-03235 : max # extents (string) reached in table string.string subpartition string
  • ora-25125 : BUFFER_POOL storage option not allowed
  • ora-19590 : conversation already active
  • ora-28026 : user with same external name already exists
  • 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.