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 : 23-05-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-06733 : TLI Driver: failed to receive disconnect
  • ora-26056 : Requested direct path operation on a view is not supported.
  • ora-06817 : TLI Driver: could not read the Novell network address
  • ora-02052 : remote transaction failure at string
  • ora-30365 : left relation in the JOIN KEY clause cannot be same as right
  • ora-02243 : invalid ALTER INDEX or ALTER MATERIALIZED VIEW option
  • ora-23416 : table "string"."string" does not contain a primary key constraint
  • ora-16242 : Processing logfile (thread# string, sequence# string)
  • ora-00452 : foreground process unexpectedly terminated with error string
  • ora-02043 : must end current transaction before executing string
  • ora-12706 : this CREATE DATABASE character set is not allowed
  • ora-01267 : Failure getting date/time
  • ora-32805 : identifier for string too long, maximum length is string characters
  • ora-12467 : minimum label can contain a level only
  • ora-13365 : layer SRID does not match geometry SRID
  • ora-32633 : MODEL subquery FOR cell index returns too many rows
  • ora-40205 : invalid setting name string
  • ora-01272 : REUSE only allowed when a file name is provided.
  • ora-32032 : free temporary object number not available
  • ora-36679 : (XSDPART17) workspace object contains a leaf (workspace object) that is not part of the partition dimension workspace object.
  • ora-12012 : error on auto execute of job string
  • ora-38413 : elementary attribute name may not be longer than 32 characters
  • ora-28553 : pass-through SQL: invalid bind-variable position
  • ora-06745 : TLI Driver: listener already running
  • ora-25966 : join index cannot be based on an index organized table
  • ora-23413 : table "string"."string" does not have a materialized view log
  • ora-12088 : cannot online redefine table "string"."string" with unsupported datatype
  • ora-12350 : database link being dropped is still mounted
  • ora-01955 : DEFAULT ROLE 'string' not granted to user
  • ora-01982 : invalid auditing option for tables
  • 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.