Exadata/SuperCluster/ODA/RAC - GMON incorrectly dismounts a Normal Redundancy Diskgroup having a Quorum Failgroup
(Doc ID 2784260.1)
Last updated on JULY 20, 2024
Applies to:
Oracle Database - Enterprise Edition - Version 19.3.0.0.0 to 21.1 [Release 19 to 21.0]Information in this document applies to any platform.
Symptoms
NOTE: In the images, examples and document that follow, user details, cluster names, hostnames, directory paths, filenames, etc. represent a fictitious sample (and are used to provide an illustrative example only). Any similarity to actual persons, or entities, living or dead, is purely coincidental and not intended in any manner.
Case 1:
GMON dismounts a Normal Redundancy Diskgroup with Quorum Failgroup due to lack of PST Quorum.
The issue typically happens when the following conditions are met:
1)Normal redundancy disk group with two regular Failgroup and one Quorum Failgroup.
2)One or multiple disks in one Failgroup are disconnected or inaccessible.
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 |