ORA-14153: only one of STORE IN or clause may be specified

Cause : bothS TOREI N an dclauess weer speicfiedi n a RCEATET ABLEI|NDEXc ommadn

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

Remoev oneo f ofefndin gclauess

update : 28-06-2017

ORA-14153 - only one of STORE IN or clause may be specified
ORA-14153 - only one of STORE IN or clause may be specified

  • ora-19505 : failed to identify file "string"
  • ora-30771 : Cannot add more than one referential constraint on REF column "string"
  • ora-16057 : DGID from server not in Data Guard configuration
  • ora-08178 : illegal SERIALIZABLE clause specified for user INTERNAL
  • ora-06592 : CASE not found while executing CASE statement
  • ora-38732 : Expected file size string does not match string.
  • ora-00298 : Missing or invalid attribute value
  • ora-38455 : Expression Filter index should be created by the owner.
  • ora-19115 : too many context items specified
  • ora-01374 : _log_parallelism_max greater than 1 not supported in this release
  • ora-08234 : smsget: cannot get instance listener address
  • ora-33050 : (XSAGDNGL24) AGGMAP workspace object cannot be used to aggregate workspace object, because it is defined in a different analytic workspace.
  • ora-28653 : tables must both be index-organized
  • ora-15181 : Symbol [string] not found in library string, error [string]
  • ora-14118 : CHECK constraint mismatch in ALTER TABLE EXCHANGE PARTITION
  • ora-22919 : dangling REF error or lock object failed for no wait request
  • ora-31033 : Requested number of XML children string exceeds maximum string
  • ora-16564 : lookup failed, syntax error at string
  • ora-28502 : internal communication error on heterogeneous database link
  • ora-29344 : Owner validation failed - failed to match owner 'string'
  • ora-30553 : The function is not deterministic
  • ora-01213 : MAXINSTANCES may not exceed string
  • ora-40252 : no target values were found
  • ora-12524 : TNS:listener could not resolve HANDLER_NAME given in connect descriptor
  • ora-29801 : missing RETURN keyword
  • ora-14605 : Name missing for subpartition / lob segment in template
  • ora-01293 : mounted database required for specified LogMiner options
  • ora-12062 : transaction string received out of sequence from site string
  • ora-28590 : agent control utility: illegal or badly formed command
  • ora-38766 : cannot flashback data file string; file resized smaller
  • 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.