ORA-15104: conflicting CONTENTS options

Cause : The command specified conflicting or duplicate INCLUDING CONTENTS or EXCLUDING CONTENTS options.

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

Specify only one option.

update : 22-08-2017
ORA-15104

ORA-15104 - conflicting CONTENTS options
ORA-15104 - conflicting CONTENTS options

  • ora-28358 : improper set key syntax
  • ora-19320 : Host name not specified in HTTP URL
  • ora-30394 : source statement identical to the destination statement
  • ora-07511 : sscggtl: $enq unexpected return for master termination lock
  • ora-02188 : Cannot enable instance publicly
  • ora-23307 : replicated schema string already exists
  • ora-32506 : expecting one of string, string, or string but found string
  • ora-00302 : limit of string logs exceeded
  • ora-14326 : Primary index on an IOT, DOMAIN and LOB indexes may not be specified in the UPDATE INDEXES clause
  • ora-37020 : (XSMULTI01) Analytic workspace string is not in MULTI mode.
  • ora-16206 : database already configured as Logical Standby database
  • 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-31401 : change source string is not an existing change source
  • ora-03292 : Table to be truncated is part of a cluster
  • ora-22292 : Cannot open a LOB in read-write mode without a transaction
  • ora-19671 : media management software returned invalid proxy handle
  • ora-36972 : (XSRELTBL13) Relation workspace object must be dimensioned by workspace object.
  • ora-24803 : illegal parameter value in lob read function
  • ora-09776 : pws_look_up: access error on (Oracle helper) executable
  • ora-24194 : attempt to read data in a message as the wrong type
  • ora-25350 : maximum number of concurrent transaction branches exceeded
  • ora-13450 : GeoRaster metadata layerInfo error
  • ora-30682 : improper value for argument OPTION_FLAGS
  • ora-01342 : LogMiner can not resume session due to inability of staging checkpointed data
  • ora-19952 : database should be mounted exclusively
  • ora-19556 : required destination LOG_ARCHIVE_DUPLEX_DEST currently is deferred
  • ora-13480 : the Source Type is not supported
  • ora-06311 : IPA: Maximum number of servers reached
  • ora-12323 : unable to open database (link name string)
  • ora-07586 : spdcr: $SEARCH failure
  • 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.