Database Tutorials MSSQL, Oracle, PostgreSQL, MySQL, MariaDB, DB2, Sybase, Teradata, Big Data, NOSQL, MongoDB, Couchbase, Cassandra, Windows, Linux 
The database instances can be closed with an “ASMB terminating” error due to a bug. The error codes are ORA-15064 and ORA-03113.
Possible errors on the database side will be as follows.
1 2 3 4 | ORA-15064: communication failure with ASM instance ORA-03113: end-of-file on communication channel ASMB (ospid: 10551): terminating the instance due to error 15064 Instance terminated by ASMB, pid = 10551 |
You can also see the following errors in ASM logs.
1 2 3 4 5 6 7 8 | NOTE: client exited [9030]NOTE: ASMB process exiting, either shutdown is in progress NOTE: or foreground connected to ASMB was killed. Wed Feb 25 07:06:02 2015 PMON (ospid: 8942): terminating the instance due to error 481 Wed Feb 25 07:06:02 2015 ORA-1092 : opitsk aborting process Wed Feb 25 07:06:03 2015 |
The issue is corrected in version 11.2.0.4. It is necessary to apply patches to previous databases from this version.
To solve this problem, patch 13914613 must be applied.
Or the existing database should be upgraded to version 11.2.0.4.
