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 : 17-08-2017

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-12589 : TNS:connection not bequeathable
  • ora-38304 : missing or invalid user name
  • ora-38430 : Operation "string" not supported in the current release.
  • ora-04070 : invalid trigger name
  • ora-01269 : Destination parameter string is too long
  • ora-34871 : (PERMIT06) Session-only value 'value' of workspace object has been deleted because a PERMIT change has revealed a duplicate value.
  • ora-16641 : failure to acquire broker configuration metadata lock
  • ora-24157 : duplicate variable name string
  • ora-34346 : (MXDSS04) The string analytic workspace cannot be detached.
  • ora-31439 : subscription is already active
  • ora-40285 : label not in the model
  • ora-07594 : spiip: $GETJPIW failure
  • ora-19512 : file search failed
  • ora-01907 : TABLESPACE keyword expected
  • ora-32501 : Writing SGA to file failed
  • ora-17506 : I/O Error Simulation
  • ora-32109 : invalid column or parameter position
  • ora-10946 : trace name context forever
  • ora-26711 : remote table does not contain a primary key constraint
  • ora-26510 : materialized view name: 'string' is greater than max. allowed length of string bytes
  • ora-19628 : invalid SCN range
  • ora-04054 : database link string does not exist
  • ora-03248 : Too much of segment creation activity during migration
  • ora-28235 : algorithm not available
  • ora-30205 : invalid Character set
  • ora-19587 : error occurred reading string bytes at block number string
  • ora-10916 : TABLESPACE GROUP already specified
  • ora-30736 : objects in a table or view hierarchy have to be in the same schema
  • ora-13433 : GeoRaster metadata default RGB error
  • ora-29336 : Internal error [string] [string] from DBMS_PLUGTS
  • 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.