"waiting for instance recovery of group" messages appear in ASM alert.log repeatedly
(Doc ID 2419249.1)
Last updated on FEBRUARY 27, 2019
Applies to:
Oracle Exadata Storage Server Software - Version 11.1.0.3.0 to 12.2.1.1.6 [Release 11.1 to 12.2]Information in this document applies to any platform.
Symptoms
When DB server is rebooted forcibly, following messages appear in alert.log of ASM instance on existing nodes.
2018-03-01T00:37:35.154168+09:00
NOTE: waiting for instance recovery of group 2
2018-03-01T00:37:35.466304+09:00
NOTE: waiting for instance recovery of group 1
2018-03-01T00:37:35.510205+09:00
NOTE: waiting for instance recovery of group 1
2018-03-01T00:37:36.018153+09:00
NOTE: waiting for instance recovery of group 2
2018-03-01T00:37:38.154226+09:00
NOTE: waiting for instance recovery of group 2
NOTE: waiting for instance recovery of group 2
2018-03-01T00:37:35.466304+09:00
NOTE: waiting for instance recovery of group 1
2018-03-01T00:37:35.510205+09:00
NOTE: waiting for instance recovery of group 1
2018-03-01T00:37:36.018153+09:00
NOTE: waiting for instance recovery of group 2
2018-03-01T00:37:38.154226+09:00
NOTE: waiting for instance recovery of group 2
While these messages appear in alert.log of ASM instances, GMON process of ASM instances wait for "kfk: async disk IO".
And on DB instances, SMON process may receive ORA-240.
Changes
This problem may occur when voting disks are placed under Quorum Disk on Exadata environment.
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Changes |
Cause |
Solution |
References |