ORA-13918: Updating system alert with reason_id string failed; previous alert not found

Cause : System Error: An attempt to update a system alert failed. The alert was improperly cleared from WRI$_ALERT_OUTSTANDING.

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

Do not delete from WRI$_ALERT_OUTSTANDING. If this condition repeats, please contact Oracle Support.

update : 25-06-2017

ORA-13918 - Updating system alert with reason_id string failed; previous alert not found
ORA-13918 - Updating system alert with reason_id string failed; previous alert not found

  • ora-22995 : TABLESPACE DEFAULT option is invalid in this context
  • ora-12415 : A column of another datatype exists on the specified table
  • ora-22369 : invalid parameter encountered in method string
  • ora-29550 : Java session state cleared
  • ora-15051 : file 'string' contains string error(s)
  • ora-32405 : cannot alter tablespace for existing materialized view log
  • ora-28668 : cannot reference mapping table of an index-organized table
  • ora-16505 : site ID is invalid
  • ora-16810 : multiple errors or warnings detected for the database
  • ora-23613 : Script string already exists
  • ora-02218 : invalid INITIAL storage option value
  • ora-31496 : must use DBMS_CDC_PUBLISH.DROP_CHANGE_TABLE to drop change tables
  • ora-00911 : invalid character
  • ora-14187 : partitioning method for LOCAL index is inconsistent with that of the underlying table
  • ora-22618 : attribute is a BAD NULL in the image handle
  • ora-07629 : smpall: $EXPREG failure
  • ora-12726 : unmatched bracket in regular expression
  • ora-16127 : stalled waiting for additional transactions to be applied
  • ora-23438 : missing refresh group template
  • ora-27303 : additional information: string
  • ora-19322 : An error occurred while reading from host (string): port (string)
  • ora-16741 : the destination parameter of standby database "string" has incorrect syntax
  • ora-24801 : illegal parameter value in OCI lob function
  • ora-12081 : update operation not allowed on table "string"."string"
  • ora-37071 : You may not execute a parallel OLAP operation against updated but uncommitted AW string.
  • ora-03245 : Tablespace has to be dictionary managed, online and permanent to be able to migrate
  • ora-14155 : missing PARTITION or SUBPARTITION keyword
  • ora-16094 : database shutdown during archival operation
  • ora-38733 : Physical size string less than needed string.
  • ora-31502 : invalid number supplied for supplemental_processes
  • 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.