ORA-12400: invalid argument to facility error handling

Cause : An argument to a facility error handling function exceeded a maximum limit or referred to an invalid product/facility.

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

Specify a valid facility error handling parameter value.

update : 21-08-2017
ORA-12400

ORA-12400 - invalid argument to facility error handling
ORA-12400 - invalid argument to facility error handling

  • ora-09828 : SCLFR: atomic latch return error.
  • ora-32502 : Cannot execute command. Flash Freeze is not in effect
  • ora-14176 : this attribute may not be specified for a hash partition
  • ora-13217 : invalid parameters supplied in ALTER INDEX statement
  • ora-01204 : file number is string rather than string - wrong file
  • ora-02363 : error reading from file: string
  • ora-39169 : Local version of string cannot work with remote version of string.
  • ora-19017 : Attributes can only be simple scalars
  • ora-24183 : invalid transformation
  • ora-31483 : cannot have spaces in the parameter string
  • ora-13053 : maximum number of geometric elements in argument list exceeded
  • ora-00360 : not a logfile member: string
  • ora-02488 : Error encountered when accessing file [string] for trace conversion
  • ora-25407 : connection terminated
  • ora-29902 : error in executing ODCIIndexStart() routine
  • ora-02719 : osnfop: fork failed
  • ora-30515 : suspend triggers cannot have BEFORE type
  • ora-37144 : (MDQUERY01) string is not a valid metadata object type for MDQUERY.
  • ora-32302 : object materialized views must be object ID based
  • ora-29380 : resource plan string is currently active and cannot be deleted
  • ora-12600 : TNS: string open failed
  • ora-16631 : operation requires shutdown of database/instance "string"
  • ora-07597 : spguns: $GETJPIW failure
  • ora-08197 : Flashback Table operation is not supported on clustered tables
  • ora-16251 : LSP1 Background Build not permitted
  • ora-24065 : propagation for QUEUE string and DESTINATION string already disabled
  • ora-14700 : Object(s) owned by SYS cannot be locked by non-SYS user
  • ora-30727 : duplicate referential constraint for a REF column
  • ora-15063 : ASM discovered an insufficient number of disks for diskgroup "string"
  • ora-30358 : summary and materialized view are not in same schema
  • 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.