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 : 25-04-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-01048 : Couldn't find the specified procedure in the given context
  • ora-31224 : DBMS_LDAP: invalid LDAP session
  • ora-25230 : invalid value string, WAIT should be non-negative
  • ora-29815 : object being associated is not present
  • ora-30478 : Specified dimension does not exist
  • ora-30572 : AUTO segment space management not valid with DICTIONARY extent management
  • ora-30332 : container table already in use by other summary
  • ora-22925 : operation would exceed maximum size allowed for a LOB value
  • ora-06976 : X.25 Driver: endpoint creation failure
  • ora-22885 : cannot get REF to a non-persistent object
  • ora-14283 : UNIQUE constraints mismatch in ALTER TABLE EXCHANGE SUBPARTITION
  • ora-37122 : AW Session cache disabled
  • ora-19763 : compatibility version string is higher than maximum allowed: string
  • ora-19624 : operation failed, retry possible
  • ora-13622 : invalid recommendation annotation
  • ora-24164 : invalid rule engine system privilege: string
  • ora-38705 : Expected block size string does not match string in log header.
  • ora-27077 : too many files open
  • ora-30502 : system triggers cannot have INSERT, UPDATE, or DELETE as triggering events
  • ora-33046 : (XSAGDNGL22) In AGGMAP workspace object, you can specify only one SCREENBY clause.
  • ora-19923 : the session for row with id string is not active
  • ora-03132 : two-task default value overflow
  • ora-25527 : bad format of _DB_MTTR_SIM_TARGET
  • ora-40104 : invalid training data for model build
  • ora-37027 : (XSMLTRESYNC02) Object workspace object cannot be resynced without modified object workspace object because they share a modified composite dimension.
  • ora-13628 : Insufficient privileges to access the task belonging to the specified user
  • ora-24074 : RETRY_DELAY and MAX_RETRIES cannot be used for exception queue %.string
  • ora-13829 : SQL profile named string already exists
  • ora-08314 : sllfcf: Error closing file
  • ora-19907 : recovery time or SCN does not belong to recovered incarnation
  • 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.