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 : 30-04-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-08412 : error encountered in WMSGBSIZ, size for WMSGBLK is not big enough for warning message
  • ora-29934 : index specified for association is not a domain index
  • ora-00607 : Internal error occurred while making a change to a data block
  • ora-21707 : pin duration is longer than allocation duration
  • ora-02436 : date or system variable wrongly specified in CHECK constraint
  • ora-07682 : sou2os: set kernel dispatch fail err
  • ora-19507 : failed to retrieve sequential file, handle="string", parms="string"
  • ora-01141 : error renaming data file string - new file 'string' not found
  • ora-30677 : session is already connected to a debugger
  • ora-16786 : resource guard cannot access Data Guard broker metadata
  • ora-19674 : file string is already being backed up with proxy copy
  • ora-02722 : osnpui: cannot send break message to orapop
  • ora-04002 : INCREMENT must be a non-zero integer
  • ora-31688 : Worker process string failed during startup.
  • ora-24337 : statement handle not prepared
  • ora-01187 : cannot read from file string because it failed verification tests
  • ora-19666 : cannot do incremental restore of the control file
  • ora-02331 : cannot create constraint on column of datatype string
  • ora-01500 : failure in getting date/time
  • ora-01286 : start interval required
  • ora-31419 : source table string does not exist
  • ora-19771 : cannot rename change tracking file while database is open
  • ora-01313 : LogMiner dictionary column type different from specified type
  • ora-27075 : SSTMOFRC constant too large
  • ora-30039 : Cannot drop the undo tablespace
  • ora-01968 : Only specify RESETLOGS or NORESETLOGS once
  • ora-16252 : Rebuild operation not permitted
  • ora-28337 : the specified index may not be defined on an encrypted column
  • ora-02259 : duplicate UNIQUE/PRIMARY KEY specifications
  • ora-39125 : Worker unexpected fatal error in string while calling string [string]
  • 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.