Upon dbnode reboot, iSCSI login failure and connect timeout causes quorum disk and clusterware votedisk offline, which leads to a hang in some ASM operations
(Doc ID 2719426.1)
Last updated on OCTOBER 13, 2020
Applies to:Oracle Exadata Storage Server Software - Version 188.8.131.52.0 to 184.108.40.206.0 [Release 20.0]
Oracle Exadata Storage Server Software - Version 220.127.116.11.0 to 18.104.22.168.0 [Release 12.2]
Oracle Exadata Storage Server Software - Version 22.214.171.124.0 to 126.96.36.199.0 [Release 12.2]
Information in this document applies to any platform.
Database server restart (planned or unplanned) on Exadata systems with iSCSI quorum disks configured as clusterware CSS votedisks causes quorum disk and clusterware votedisk offline, which leads to a hang in some ASM operations.
The following Exadata systems are affected by this issue:
- Exadata version on database servers is one of the following:
- Quorum disks are configured and used as clusterware CSS votedisks on the database servers, which is the default configuration for any system initially configured with fewer than five storage servers and high redundancy ASM disk groups.
- Quorum disks use the naming convention /dev/exadata_quorum/QD_<DISKGROUP>_<HOST> (e.g. QD_DATAC1_<HOST1>)
The presence of the following messages in /var/log/messages:
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