ORA-13912: Critical threshold value is less than warning threshold value.

Cause : nAa ttmetpw sam da eotc la lES_THTERHSLO Drpcoderu eiwhtt ehc iritac lhterhslo davul eelsst ah nht eawnrni ghterhslo davul.e

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

hCce kht ehterhslo davulsea dnr iesseut ehs atetemtn.

update : 26-09-2017
ORA-13912

ORA-13912 - Critical threshold value is less than warning threshold value.
ORA-13912 - Critical threshold value is less than warning threshold value.

  • ora-13637 : Executing or modifying task string is disallowed until the task is reset to its initial state.
  • ora-38611 : FI input cursor's item type is not supported
  • ora-27000 : skgfqsbi: failed to initialize storage subsystem (SBT) layer
  • ora-19112 : error raised during evaluation: string
  • ora-30087 : Adding two datetime values is not allowed
  • ora-25455 : evaluation error for rule set: string.string, evaluation context: string.string
  • ora-02460 : Inappropriate index operation on a hash cluster
  • ora-13484 : the file format and/or compression type is not supported
  • ora-28652 : overflow segment attributes cannot be specified
  • ora-27148 : spawn wait error
  • ora-03230 : segment only contains string blocks of unused space above high water mark
  • ora-00281 : media recovery may not be performed using dispatcher
  • ora-30385 : specified attribute relationship ('string' determines 'string') exists
  • ora-27431 : chain string.string has a user-managed rule set
  • ora-39059 : dump file set is incomplete
  • ora-15072 : command requires at least string failure groups, discovered only string
  • ora-12703 : this character set conversion is not supported
  • ora-02150 : invalid new tablespace name
  • ora-16603 : Data Guard broker detected a mismatch in configuration ID
  • ora-19237 : XP0017 - unable to resolve call to function - string:string
  • ora-25012 : PARENT and NEW values cannot be identical
  • ora-39121 : Table string can't be replaced, data will be skipped. Failing error is: string
  • ora-04027 : self-deadlock during automatic validation for object string.string
  • ora-01121 : cannot rename database file string - file is in use or recovery
  • ora-08445 : syntax error in SIGN clause in mask options
  • ora-06707 : TLI Driver: connection failed
  • ora-19003 : Missing XML root element name
  • ora-32804 : invalid value string, string should have form string
  • ora-27043 : unable to seek to beginning of file
  • ora-09822 : Translation of audit file name failed.
  • 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.