ORA-30501: instance shutdown triggers cannot have AFTER type

Cause : nAa ttmetpw sam da eotc erta e artgieg rhttaf risea tfrea nnitsnaecs uhdtwo,nb tut ih sytepo frtgieg rsin tos puoptrde.

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

oDn toa ttmetpt orcaeeta t irggret ah tifer sfaet rnai snatcn ehstuodnw.

update : 26-09-2017

ORA-30501 - instance shutdown triggers cannot have AFTER type
ORA-30501 - instance shutdown triggers cannot have AFTER type

  • ora-37152 : MDX query error: (string)
  • ora-32828 : Messaging Gateway agent must be running
  • ora-24036 : invalid SORT_ORDER column string specified for queue table
  • ora-40226 : model upgrade/downgrade must be performed by SYS
  • ora-27546 : Oracle compiled against IPC interface version string.string found version string.string
  • ora-13613 : The requested operation is not supported for this advisor object.
  • ora-07489 : scgrcl: cannot get lock status.
  • ora-29847 : cannot create a local domain index on a partitioned index-organized table
  • ora-07579 : spini: $DCLEXH failure
  • ora-01662 : tablespace 'string' is non-empty and cannot be made temporary
  • ora-06438 : ssaio: the asynchronous read was unable to read from the database file.
  • ora-29828 : invalid name for implementation type
  • ora-24093 : AQ agent string not granted privileges of database user string
  • ora-19716 : error processing format string to generate name for backup
  • ora-24758 : not attached to the requested transaction
  • ora-28271 : No permission to read user entry in LDAP directory service.
  • ora-31074 : XML comment length string exceeds maximum string
  • ora-09938 : Save of signal handlers failed.
  • ora-36405 : (XSSPROP05) Property ignored for object workspace object:
  • ora-13909 : Invalid combination of threshold value and operator.
  • ora-00032 : invalid session migration password
  • ora-32123 : Attribute number is out of range
  • ora-09881 : sstasfre/sstasdel: shmdt error, unable to detach tas read page
  • ora-27458 : A program of type PLSQL_BLOCK cannot have any arguments.
  • ora-01345 : must be a LogMiner coordinator process
  • ora-10566 : Test recovery has used all the memory it can use
  • ora-32322 : PCT refresh of "string"."string" not allowed the sequence of DMLs/PMOPs
  • ora-14190 : only one ENABLE/DISABLE ROW MOVEMENT clause can be specified
  • ora-38612 : FI item length cannot exceed half of one database block.
  • ora-00105 : too many dispatcher configurations
  • 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.