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 : 20-07-2017
ORA-15082

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

  • ora-16771 : failover to a physical standby database failed
  • ora-12018 : following error encountered during code generation for "string"."string"
  • ora-07504 : scgcmn: $hiber unexpected return
  • ora-19955 : only one open thread is allowed to change the DBID
  • ora-00054 : resource busy and acquire with NOWAIT specified
  • ora-02473 : Error while evaluating the cluster's hash expression.
  • ora-09715 : orasrv: cannot obtain puname
  • ora-29389 : too many errors during validation
  • ora-02212 : duplicate PCTFREE option specification
  • ora-10389 : parallel query server interrupt (cleanup)
  • ora-14118 : CHECK constraint mismatch in ALTER TABLE EXCHANGE PARTITION
  • ora-24960 : the attribute string is greater than the maximum allowable length of number
  • ora-01076 : multiple logons per process not yet supported
  • ora-22857 : cannot modify columns of object tables
  • ora-24439 : success with PLSQL compilation warning
  • ora-31437 : duplicate change set string
  • ora-23377 : bad name string for missing_rows_oname1 argument
  • ora-01078 : failure in processing system parameters
  • ora-15026 : disk 'string' is not an ASM disk
  • ora-03297 : file contains used data beyond requested RESIZE value
  • ora-12525 : TNS:listener has not received client's request in time allowed
  • ora-38453 : ExpFilter index should be created in the same schema as the base table.
  • ora-38607 : FI minimum and maximum itemset length not between [1, string]
  • ora-28339 : missing or invalid encryption algorithm
  • ora-28541 : Error in HS init file on line number.
  • ora-01595 : error freeing extent (string) of rollback segment (string))
  • ora-07587 : spdcr: $CREPRC failure
  • ora-25216 : invalid recipient, either NAME or ADDRESS must be specified
  • ora-37139 : (XSCCOMP14) Cannot AGGREGATE workspace object using AGGMAP workspace object because you can not AGGREGATE a variable dimensioned by a COMPRESSED COMPOSITE using an AGGMAP with a PROTECT clause.
  • ora-25456 : rule set was modified or evaluation terminated for iterator: string
  • 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.