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 : 27-06-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-01411 : cannot store the length of column in the indicator
  • ora-14618 : cannot drop the last value of subpartition
  • ora-40207 : duplicate or multiple function settings
  • ora-19646 : cannot change size of datafile string from string to string
  • ora-25244 : dequeue index key not found, QUEUE string, rowid string
  • ora-30060 : Internal event for RECO tracing
  • ora-28231 : no data passed to obfuscation toolkit
  • ora-01581 : attempt to use rollback segment (string) new extent (string) which is being allocated
  • ora-33454 : (ESDREAD07) Discarding compiled code for workspace object because number is now string workspace object, whereas it was string workspace object when the code was compiled.
  • ora-01533 : cannot rename file 'string'; file does not belong to tablespace
  • ora-27543 : Failed to cancel outstanding IPC request
  • ora-02162 : invalid value for MAXDATAFILES
  • ora-28538 : result set not found
  • ora-13499 : %s
  • ora-07598 : spwat: $SETIMR failure
  • ora-15048 : ASM internal files cannot be deleted
  • ora-37069 : You may not execute a parallel OLAP operation against the EXPRESS AW.
  • ora-08446 : syntax error in SYNCHRONIZED clause in mask options
  • ora-01311 : Illegal invocation of the mine_value function
  • ora-27001 : unsupported device type
  • ora-02256 : number of referencing columns must match referenced columns
  • ora-27018 : BLKSIZE is not a multiple of the minimum physical block size
  • ora-10636 : ROW MOVEMENT is not enabled
  • ora-03130 : the buffer for the next piece to be fetched is required
  • ora-16075 : standby database destination mismatch
  • ora-08321 : scnmin: NOT IMPLEMENTED YET
  • ora-13191 : failed to read SDO_ORDCNT value
  • ora-24186 : wrong object type, could not transform message
  • ora-24351 : invalid date passed into OCI call
  • ora-01470 : In-list iteration does not support mixed operators
  • 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.