Exadata: Clusterware crash on DB nodes after a cell outage/reboot when the RDBMS ADR diag destination is on ACFS
(Doc ID 2344244.1)
Last updated on SEPTEMBER 27, 2021
Applies to:Oracle Database Cloud Schema Service - Version N/A and later
Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Backup Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Information in this document applies to any platform.
Clusterware on the Exadata DB nodes may crash after a cell reboot/outage. The issue may affect all the DB nodes in the cluster, and can cause a complete outage in the environment.
The clusterware CSSD trace would indicate that the crash occurred due to the fence timeout, and the fence timeout occurred due to the reason that the diskmon was waiting for the acknowledments from the slave diskmons running on ASM/RDBMS side.
ADR diag destination is moved to ACFS.
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