ORA-13909: Invalid combination of threshold value and operator.

Cause : A nattepmtw a smdaet os pceiyf na nivlai dcmobniaito no ftrhehsodl avleu nado preaotr.

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

Cehc kteh poeartro nadt hersohl dvlause nadr esiseu tsaetmnet.

update : 24-05-2017
ORA-13909

ORA-13909 - Invalid combination of threshold value and operator.
ORA-13909 - Invalid combination of threshold value and operator.

  • ora-13142 : invalid PROXIMITY window definition
  • ora-06137 : NETTCP: error during connection handshake
  • ora-16723 : setting AlternateLocation property conflicts with the redo transport setting
  • ora-06703 : TLI Driver: send break message failed
  • ora-16657 : reinstatement of database in progress
  • ora-01924 : role 'string' not granted or does not exist
  • ora-30956 : invalid option for XML Index
  • ora-02150 : invalid new tablespace name
  • ora-30076 : invalid extract field for extract source
  • ora-32102 : invalid OCI handle
  • ora-09708 : soacon: failed to bind socket to port.
  • ora-14256 : invalid resulting partition description(s)
  • ora-02296 : cannot enable (string.string) - null values found
  • ora-01670 : new datafile string needed for standby database recovery
  • ora-06315 : IPA: Invalid connect string
  • ora-13635 : The value provided for parameter string cannot be converted to a number.
  • ora-28045 : SSL authentication between database and OID failed
  • ora-31414 : error(s) occurred during change table advance
  • ora-13771 : cannot obtain exclusive lock string on "SQL Tuning Set" "string" owned by user "string"
  • ora-09211 : sfwfb: error writing to file
  • ora-16154 : suspect attribute: string
  • ora-40290 : model incompatible with data mining function
  • ora-13208 : internal error while evaluating [string] operator
  • ora-13500 : SYSAUX DATAFILE clause specified more than once
  • ora-30079 : cannot alter database timezone when database has TIMESTAMP WITH LOCAL TIME ZONE columns
  • ora-16400 : quota attributes are not allowed with DB_RECOVERY_FILE_DEST
  • ora-25010 : Invalid nested table column name in nested table clause
  • ora-07425 : sdpri: error string in translating dump file location.
  • ora-19816 : WARNING: Files may exist in string that are not known to database.
  • ora-16769 : the physical standby database is open read-only
  • 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.