ORA-12076: invalid threshold value

Cause : Ther esutl se tthrsehol dor OLB trheshlod vlaue si no tsupoprte.d

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

Speicfy athrsehol dvaleu beolw 6K4.

update : 25-04-2017
ORA-12076

ORA-12076 - invalid threshold value
ORA-12076 - invalid threshold value

  • ora-01105 : mount is incompatible with mounts by other instances
  • ora-23602 : Invalid streams process type string
  • ora-15104 : conflicting CONTENTS options
  • ora-24396 : invalid attribute set in server handle
  • ora-32506 : expecting one of string, string, or string but found string
  • ora-36208 : (XSAGOP05N) In AGGMAP workspace object, you can only specify NAOPERATOR string with the PROPORTIONAL or EVEN operators, not string.
  • ora-16087 : graceful switchover requires standby or current control file
  • ora-28173 : certificate not provided by proxy
  • ora-23498 : repgroups specified must have the same masters
  • ora-36980 : (XSRELGID02) Variable workspace object must have a numeric data type.
  • ora-10979 : trace flags for join index implementation
  • ora-31622 : ORACLE server does not have string access to the specified file
  • ora-14613 : Attempt to generate name from parent name string and template name string failed as the combine named would have been longer than allowed
  • ora-16821 : logical standby database dictionary not yet loaded
  • ora-39178 : cannot perform estimate on metadata only jobs
  • ora-12164 : TNS:Sqlnet.fdf file not present
  • ora-32310 : object materialized views must select from an object table
  • ora-24055 : cannot delete propagation status rows that are in prepared state
  • ora-13708 : Some snapshots in the range [string, string] were purged before the analysis was complete.
  • ora-02771 : Illegal request time out value
  • ora-30340 : illegal dimension name
  • ora-00270 : error creating archive log string
  • ora-02852 : Invalid critical-section time out value
  • ora-13000 : dimension number is out of range
  • ora-27365 : job has been notified to stop, but failed to do so immediately
  • ora-34656 : (MXSQL24) Additional WHERE clause conditions with CURRENT OF syntax
  • ora-12221 : TNS:illegal ADDRESS parameters
  • ora-00216 : control file could not be resized for migration from 8.0.2
  • ora-30060 : Internal event for RECO tracing
  • ora-39219 : directory object name is too long
  • 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.