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 : 23-08-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-31464 : target table for the change table no longer exists
  • ora-00264 : no recovery required
  • ora-19724 : snapshot too old: snapshot time is before file string plug-in time
  • ora-13525 : error with computing space usage for sysaux occupant
  • ora-04052 : error occurred when looking up remote object stringstringstringstringstring
  • ora-29866 : cannot create domain index on a column of index-organized table
  • ora-36714 : (XSMXALLOC03) TARGETLOG variable workspace object must have the same data type as TARGET variable workspace object.
  • ora-09772 : osnpmetbrkmsg: message from host had incorrect message type
  • ora-22615 : attribute is not a collection
  • ora-01137 : data file string is still in the middle of going offline
  • ora-36806 : (XSTBLFUNC03) The OLAP_TABLE function refers to an invalid ADT attribute: string.
  • ora-14552 : cannot perform a DDL, commit or rollback inside a query or DML
  • ora-31066 : Insertion of string into string creates a cycle
  • ora-12010 : cannot create materialized view log on table owned by SYS
  • ora-32017 : failure in updating SPFILE
  • ora-04941 : required operating system patch needs to be applied
  • ora-02228 : duplicate SIZE specification
  • ora-00080 : invalid global area specified by level string
  • ora-00972 : identifier is too long
  • ora-14291 : cannot EXCHANGE a composite partition with a non-partitioned table
  • ora-00307 : requested INSTANCE_NUMBER out of range, maximum is string
  • ora-16623 : stale DRC UID sequence number detected
  • ora-15035 : no disks belong to diskgroup "string"
  • ora-02052 : remote transaction failure at string
  • ora-26765 : invalid parameter "string" for downstream capture "string"
  • ora-30150 : Invalid argument passed to OCIFile function
  • ora-19628 : invalid SCN range
  • ora-01316 : Already attached to a Logminer session
  • ora-22323 : error table "string"."string" does not exist
  • ora-01297 : redo version mismatch between dictionary string and logfiles
  • 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.