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-06-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-22954 : This multiset operation is not supported for this element type.
  • ora-01594 : attempt to wrap into rollback segment (string) extent (string) which is being freed
  • ora-30565 : Only one INVALIDATE or UPDATE GLOBAL INDEXES clause may be specified
  • ora-01212 : MAXLOGMEMBERS may not exceed string
  • ora-13115 : [string]_EDGE$ table does not exist
  • ora-26672 : timeout occurred while stopping STREAMS process string
  • ora-01230 : cannot make read only - file string is offline
  • ora-00399 : corrupt change description in redo log
  • ora-07206 : slgtd: gettimeofday error, unable to obtain time.
  • ora-29555 : Java source, class or resource is not allowed here
  • ora-16023 : system string destination cannot be the same as session string destination
  • ora-25272 : Signature does not exist for the given reciever and message id.
  • ora-12634 : Memory allocation failed
  • ora-32609 : missing REFERENCE keyword in MODEL clause
  • ora-23485 : Column group "string" must consist of a single numeric column only
  • ora-23538 : cannot explicitly refresh a NEVER REFRESH materialized view ("string")
  • ora-36188 : (XSAGGR16) AGGREGATE read a value less than 1 out of COUNTVAR variable workspace object. Either the values of the COUNTVAR variable are stored improperly, or there is problem in AGGREGATE. If no one has modified the values in this COUNTVAR, contact Oracle customer support.
  • ora-19512 : file search failed
  • ora-19103 : VALUE keyword keyword
  • ora-02763 : Unable to cancel at least one request
  • ora-32305 : RepAPI materialized views with user-defined types are not supported
  • ora-24763 : transaction operation cannot be completed now
  • ora-36272 : (XSCGMDLAGG04) 'workspace object' is not a valid operator for the AGGREGATION function.
  • ora-08175 : discrete transaction restriction violated (string)
  • ora-00568 : Maximum number of interrupt handlers exceeded
  • ora-30625 : method dispatch on NULL SELF argument is disallowed
  • ora-31532 : cannot enable change source string
  • ora-00304 : requested INSTANCE_NUMBER is busy
  • ora-31670 : Username argument must be specified and non-null.
  • ora-19244 : XQ0024 - invalid attribute node in element constructor
  • 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.