RAC on Windows: How To Correctly Increase the OraFenceService Timeout Value (and avoid: 'OraFence driver has not been scheduled in the WarningTimeout period')
(Doc ID 2339930.1)
Last updated on FEBRUARY 25, 2019
Applies to:Oracle Database - Enterprise Edition - Version 126.96.36.199 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
Microsoft Windows x64 (64-bit)
Normally one should not change the default OraFenceService Timeout but sometimes it is desirable. For example, reference My Oracle Support, <Document:811271.1> - "RAC and Oracle Clusterware Best Practices and Starter Kit (Windows)"
Making such a change incorrectly can lead to very many messages in the Windows Event Viewer System log file of the form:
OR even bugchecks (for example bugchecks 0XA or 0XB8) from the orafencedrv.sys driver.
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