My Oracle Support Banner

Oracle Grid Infrastructure: How to Troubleshoot Voting Disk Evictions (Doc ID 1549428.1)

Last updated on DECEMBER 17, 2019

Applies to:

Oracle Database - Enterprise Edition - Version 11.2.0.1 and later
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
Information in this document applies to any platform.

Purpose

The clusterware must be able to access a minimum number of the voting files, otherwise it will abort.

When the node aborts for this reason, the node alert log in $GRID_HOME/log/<hostname>/alert<nodename>.log will show CRS-1606 error. For example:

The two most common causes for this issue are: (a) interruption of the storage connection to voting disk; (b) if only one voting disk is in use and version is less than 11.2.0.3.4, hitting known bug 13869978.

The purpose of this document is to provide steps to take after a voting disk eviction.

Troubleshooting Steps

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
Purpose
Troubleshooting Steps
 1. Check whether all of the voting files are currently accessible.
 2. Apply fix for 13869978 if only one voting disk is in use.
 3. Check OS, SAN, and storage logs for any errors from the time of the incident.
 4. Check archived IO statistics from the time of the incident.
 a) Collecting the archived IO statistics
 b) What to look for in the archived IO statistics
References

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.