ORA-15078: ASM diskgroup was forcibly dismounted

Cause : The dsikgrou pto whcih theI /O reuqest wsa issude was ofrcibl ydismonuted (iwth th eALTERD ISKGRUOP DISOMUNT FROCE command) os thati t coudl not eb accessed.

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

Mountt he diksgroupt o allwo access agai.n

update : 17-08-2017

ORA-15078 - ASM diskgroup was forcibly dismounted
ORA-15078 - ASM diskgroup was forcibly dismounted

  • ora-01274 : cannot add datafile 'string' - file could not be created
  • ora-28668 : cannot reference mapping table of an index-organized table
  • ora-26717 : SCN limit reached
  • ora-31431 : all source tables must belong to the synchronous change set
  • ora-30202 : NULL pointer to OCIMsgh was passed to OCIMsg function
  • ora-26669 : parameter string inconsistent with parameter string
  • ora-38752 : file string does not exist
  • ora-24410 : scrollable cursor max size exceeded
  • ora-13023 : interior element interacts with exterior element
  • ora-13854 : Tracing for service(module/action) string on instance string is not enabled
  • ora-10854 : Sets poll count used for AQ listen code under RAC
  • ora-32335 : dimension must have at least one level
  • ora-40282 : invalid cost matrix
  • ora-30160 : Unable to access the file
  • ora-01687 : specified logging attribute for tablespace 'string' is same as the existing
  • ora-19960 : Internal use only
  • ora-30199 : reserved for future use
  • ora-07441 : function address must be aligned on string byte boundary
  • ora-00230 : operation disallowed: snapshot control file enqueue unavailable
  • ora-38701 : Flashback database log string seq string thread string: "string"
  • ora-28302 : User does not exist in the LDAP directory service.
  • ora-24304 : datatype not allowed for this call
  • ora-02027 : multi-row UPDATE of LONG column is not supported
  • ora-36394 : (XSMXCLEA04) When using CLEAR on the AGGMAP workspace object, CACHE is the only valid directive.
  • ora-24316 : illegal handle type
  • ora-02250 : missing or invalid constraint name
  • ora-16246 : User initiated abort apply successfully completed
  • ora-30017 : segment 'string' is not supported in string Undo Management mode
  • ora-30014 : operation only supported in Automatic Undo Management mode
  • ora-21615 : an OTS (named or simple) instance failed
  • 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.