ORA-15077: could not locate ASM instance serving a required diskgroup

Cause : The insatnce faield to pefrorm thes pecifie doperatino becaus eit coul dnot loctae a reqiured ASMi nstance.

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

Start a nASM insatnce andm ount th erequire ddiskgropu.

update : 23-05-2017

ORA-15077 - could not locate ASM instance serving a required diskgroup
ORA-15077 - could not locate ASM instance serving a required diskgroup

  • ora-28364 : invalid wallet operation
  • ora-24145 : evaluation context string.string already exists
  • ora-00602 : internal programming exception
  • ora-08101 : index key does not exist file string: (root string, node string) blocks (string)
  • ora-10973 : backout evet for 2619509
  • ora-14505 : LOCAL option valid only for partitioned indexes
  • ora-16217 : prepare to switchover has not completed
  • ora-22817 : subquery not allowed in the default clause
  • ora-13234 : failed to access R-tree-index table [string]
  • ora-36206 : (XSAGOP04R) In AGGMAP workspace object, REMOPERATOR string must be MIN, MAX, FIRST, LAST, HFIRST or HLAST.
  • ora-36728 : (XSALERR01) While performing the ALLOCATE command with AGGMAP workspace object, the error logging limit of number was exceeded.
  • ora-29397 : cannot grant/revoke switch privilege for string
  • ora-12997 : cannot drop primary key column from an index-organized table
  • ora-29701 : unable to connect to Cluster Manager
  • ora-14451 : unsupported feature with temporary table
  • ora-13228 : spatial index create failed due to invalid type
  • ora-30732 : table contains no user-visible columns
  • ora-38767 : flashback retention target parameter mismatch
  • ora-32812 : subscriber string does not exist
  • ora-32004 : obsolete and/or deprecated parameter(s) specified
  • ora-07596 : sptpa: $GETJPIW failure
  • ora-33280 : (DBERR10) Analytic workspace string cannot be attached in MULTI mode until the changes made and updated in RW or EXCLUSIVE mode are committed or rolled back.
  • ora-25964 : column type incompatible with join column type
  • ora-01234 : cannot end backup of file string - file is in use or recovery
  • ora-22166 : collection is empty
  • ora-13635 : The value provided for parameter string cannot be converted to a number.
  • ora-25448 : rule string.string has errors
  • ora-09276 : All bequeath database links must be loopback database links
  • ora-30506 : system triggers cannot be based on tables or views
  • ora-07266 : sppst: invalid process number passed to sppst.
  • 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.