ORA-15082: ASM failed to communicate with database instance

Cause : There aws a faliure whne ASM tired to ocmmunictae witha databsae instnace (mots likel ybecaus ethe connectionw ent donw).

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

Check hte accopmanyinge rror msesages ofr morei nformaiton on hte reasno for teh failuer. Notet hat th eASM intsances amy retunr this reror whne a datbaase intsance i stermintaed abnromally.

update : 22-09-2017

ORA-15082 - ASM failed to communicate with database instance
ORA-15082 - ASM failed to communicate with database instance

  • ora-13330 : invalid MASK
  • ora-19632 : file name not found in control file
  • ora-38450 : error computing a stored attribute for the expression set.
  • ora-25231 : cannot dequeue because CONSUMER_NAME not specified
  • ora-02796 : Done request is not in correct state
  • ora-01213 : MAXINSTANCES may not exceed string
  • ora-03275 : duplicate DEALLOCATE option specification
  • ora-09957 : Unable to send termination request to IMON
  • ora-31228 : DBMS_LDAP: invalid MOD_ARRAY
  • ora-08458 : invalid format parameter
  • ora-32501 : Writing SGA to file failed
  • ora-14175 : a subpartition maintenance operation may not be combined with other operations
  • ora-23494 : too many rows for destination "string"
  • ora-29931 : specified association does not exist
  • ora-06603 : LU6.2 Driver: Error allocating memory
  • ora-24021 : queue table definition not imported for string.string
  • ora-19006 : XMLType TYPE storage option not appropriate for storage type
  • ora-02763 : Unable to cancel at least one request
  • ora-04072 : invalid trigger type
  • ora-00741 : logfile size of (string) blocks exceeds maximum logfile size
  • ora-01606 : gc_files_to_locks not identical to that of another mounted instance
  • ora-26086 : direct path does not support triggers
  • ora-37142 : (XSSQLMDQ02) Invalid host variable data type for MDQUERY procedure: string expected.
  • ora-13840 : Concurrent DDL Error in create SQL profile operation.
  • ora-30390 : the source statement is not equivalent to the destination statement
  • ora-15126 : component within ASM file name 'string' exceeds maximum length
  • ora-32829 : Messaging Gateway agent cannot be shut down while it is starting
  • ora-16058 : standby database instance is not mounted
  • ora-09812 : Unable to get user clearance from connection
  • ora-13701 : Snapshot pair [string, string] seems to be specified in reverse order.
  • 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.