ORA-13917: Posting system alert with reason_id string failed with code [string] [string]

Cause : Connection to the database is dead, or invalid parameter to alert routine.

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

If this condition repeats, please contact Oracle Support.

update : 24-04-2017
ORA-13917

ORA-13917 - Posting system alert with reason_id string failed with code [string] [string]
ORA-13917 - Posting system alert with reason_id string failed with code [string] [string]

  • ora-38456 : The attribute set "string" is in an inconsistent state.
  • ora-01207 : file is more recent than control file - old control file
  • ora-22817 : subquery not allowed in the default clause
  • ora-02782 : Both read and write functions were not specified
  • ora-06757 : TLI Driver: server got bad command
  • ora-39317 : call to DBMS_SCHEMA_COPY.VALIDATION_CHECK is not legal
  • ora-19209 : invalid or unsupported formatting argument
  • ora-09353 : Windows 32-bit Two-Task driver unable to open event semaphore
  • ora-29343 : user string (mapped from user string) does not exist in the database
  • ora-33262 : (DBERR01) Analytic workspace string does not exist.
  • ora-36830 : (XSLMGEN00) AW name cannot be NA
  • ora-00094 : %s requires an integer value
  • ora-06775 : TLI Driver: error reading break mode
  • ora-01994 : GRANT failed: password file missing or disabled
  • ora-30646 : schema for external table type must be SYS
  • ora-23325 : parameter type is not string
  • ora-13220 : failed to compare tile with the geometry
  • ora-02177 : Missing required group number
  • ora-02838 : Unable to arm signal handler for the alarm signal
  • ora-28300 : No permission to read user entry in LDAP directory service.
  • ora-06778 : TLI Driver: error sending ccode
  • ora-19691 : %s is from different database: id=string, name=string
  • ora-32308 : object materialized views must use SELECT *
  • ora-12712 : new character set must be a superset of old character set
  • ora-36157 : (XSMXAGGRCOMMIT) To use the AUTOCOMMIT keyword, you must also specify the AUTOUPDATE keyword.
  • ora-25208 : RELATIVE_MSGID must be specified if SEQUENCE_DEVIATION is BEFORE
  • ora-06979 : X.25 Driver: server cannot start oracle
  • ora-23609 : unable to find directory object for directory string
  • ora-06533 : Subscript beyond count
  • ora-06316 : IPA: Invalid database SID
  • 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.