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 : 27-05-2017
ORA-15082

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

  • ora-32128 : setDataBuffer called after fetch has started
  • ora-09945 : Unable to initialize the audit trail file
  • ora-26513 : push error: master proc. string$RP.string failed for trans:string seq:string
  • ora-19681 : block media recovery on control file not possible
  • ora-24093 : AQ agent string not granted privileges of database user string
  • ora-36726 : (XSALERR00) The character 'character' is not a valid format specifier for the ALLOCATE error log.
  • ora-12491 : DBHIGH value does not dominate DBLOW
  • ora-31672 : Worker process string died unexpectedly.
  • ora-01725 : USERENV('COMMITSCN') not allowed here
  • ora-13025 : polygon does not close
  • ora-00981 : cannot mix table and system auditing options
  • ora-13866 : Client identifier must be specified
  • ora-03112 : a server linked as single-task cannot use SQL*Net
  • ora-04033 : Insufficient memory to grow pool
  • ora-23312 : not the masterdef according to string
  • ora-32734 : Error occurred when sending Oradebug command to remote DIAGs
  • ora-06268 : NETNTT: cannot read /etc/oratab
  • ora-14067 : duplicate TABLESPACE_NUMBER specification
  • ora-14553 : cannot perform a lob write operation inside a query
  • ora-39205 : Transforms are not supported in transportable jobs.
  • ora-31160 : max substitution group size string exceeded by "string" (string) for head element "string" (string)
  • ora-14254 : cannot specify ALLOCATE STORAGE for a (Composite) Range or List partitioned table
  • ora-39024 : wrong schema specified for job
  • ora-29529 : invalid function or method call string in trigger string
  • ora-35587 : (SQLOUT20) The nesting of table functions and SQL commands has exceeded the maximum of number levels.
  • ora-30953 : XML minoccurs value (string) violated
  • ora-12489 : default label not within clearance range
  • ora-28121 : driving context does not exist
  • ora-28606 : block too fragmented to build bitmap index (string,string)
  • ora-25952 : join index must only contain inner equi-joins
  • 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.