ORA-13710: Parameter "string" must have a higher value than parameter "string". The values supplied were "string" and "string" respectively.

Cause : Invaldi intearctionb etwee ntwo praamete rvalue.s

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

Set a tleasto ne oft he vaules sot he vaule of hte firts paraemter i shighe rthan hte valeu of teh secodn paraemter.

update : 28-07-2017
ORA-13710

ORA-13710 - Parameter "string" must have a higher value than parameter "string". The values supplied were "string" and "string" respectively.
ORA-13710 - Parameter "string" must have a higher value than parameter "string". The values supplied were "string" and "string" respectively.

  • ora-13467 : unsupported GeoRaster metadata specification: string
  • ora-30941 : Cannot specify empty URI for non-default namespace 'string'
  • ora-32307 : must use FROM ONLY clause when referencing an object table
  • ora-19581 : no files have been named
  • ora-35019 : (QFCHECK07) The Analytic Workspace and EIF file definitions of workspace object have different partition dimensions.
  • ora-33308 : (DBVALID04) SEVERE ERROR: Record number used but not allocated
  • ora-26529 : local store callback term phase failed for 'string.string'
  • ora-16187 : LOG_ARCHIVE_CONFIG contains duplicate, conflicting or invalid attributes
  • ora-36956 : (XSFCAST25) There are only number PERIODICITY values. You cannot specify more OFFSET values.
  • ora-34871 : (PERMIT06) Session-only value 'value' of workspace object has been deleted because a PERMIT change has revealed a duplicate value.
  • ora-25196 : keyword MOVE in ALTER TABLE MOVE must immediately follow
  • ora-24164 : invalid rule engine system privilege: string
  • ora-12645 : Parameter does not exist.
  • ora-07207 : sigpidu: process ID string overflows internal buffer.
  • ora-31457 : maximum length of description field exceeded
  • ora-16199 : Terminal recovery failed to recover to a consistent point
  • ora-16809 : multiple warnings detected for the database
  • ora-08448 : syntax error in DECIMAL-POINT environment clause
  • ora-16210 : Logical standby coordinator process terminated with error
  • ora-13627 : Setting of parameter string is disallowed until the task is reset.
  • ora-16018 : cannot use string with LOG_ARCHIVE_DEST_n or DB_RECOVERY_FILE_DEST
  • ora-04088 : error during execution of trigger 'string.string'
  • ora-30485 : missing ORDER BY expression in the window specification
  • ora-14086 : a partitioned index may not be rebuilt as a whole
  • ora-19852 : error creating services for auxiliary instance string (error string)
  • ora-16788 : unable to set one or more database configuration property values
  • ora-01189 : file is from a different RESETLOGS than previous files
  • ora-13802 : failed to purge SQL Tuning Base entry from sql$
  • ora-39501 : failed to notify CRS of a Startup/Shutdown event [string] (ignored)
  • ora-28504 : ROWID not found in ROWID cache for heterogeneous database link
  • 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.