3/28/25, 1:37 PM Document Display

Copyright (c) 2025, Oracle. All rights reserved. Oracle Confidential.

RAC and Oracle Clusterware Best Practices and Starter Kit (Windows) (Doc ID 811271.1)

In this Document

Purpose
Scope
Details
RAC and Oracle Clusterware Best Practices and Starter Kit (Platform Independent)
RAC Platform Specific Starter Kits and Best Practices
RAC on Windows Step by Step Installation Instructions
RAC on Windows Best Practices
OS Configuration Considerations
Anti-Virus Software
Network Considerations
Storage Considerations
Hardware/Vendor Specific Considerations
Oracle Software Considerations
Installation and Upgrade and Patching
General
Community Discussions
References

APPLIES TO:

Oracle Database - Enterprise Edition - Version 10.2.0.1 and later

Microsoft Windows x64 (64-bit)

PURPOSE

The goal of the Oracle Real Application Clusters (RAC) series of Best Practice and Starter Kit notes is to provide customers
with quick knowledge transfer of generic and platform specific best practices for implementing, upgrading and maintaining
an Oracle RAC system. This document is compiled and maintained based on Oracle's experience with its global RAC
customer base.

This Starter Kit is not meant to replace or supplant the Oracle Documentation set, but rather, it is meant as a supplement
to the same. It is imperative that the Oracle Documentation be read, understood, and referenced to provide answers to
any questions that may not be clearly addressed by this Starter Kit.

All recommendations should be carefully reviewed by your own operations group and should only be implemented if the
potential gain as measured against the associated risk warrants implementation. Risk assessments can only be made with
a detailed knowledge of the system, application, and business environment.

As every customer environment is unique, the success of any Oracle Database implementation, including implementations
of Oracle RAC, is predicated on a successful test environment. It is thus imperative that any recommendations from this
Starter Kit are thoroughly tested and validated using a testing environment that is a replica of the target production
environment before being implemented in the production environment to ensure that there is no negative impact
associated with the recommendations that are made.

SCOPE

This article applies to all new and existing RAC implementations as well as RAC upgrades.

https://support.oracle.com/epmos/faces/SearchDocDisplay?_adf.ctrl-state=rknd6nmnx_4 1/8
3/28/25, 1:37 PM Document Display

DETAILS

RAC and Oracle Clusterware Best Practices and Starter Kit (Platform Independent)

The following document focuses on RAC and Oracle Clusterware Best Practices that are applicable to all platforms including
a technical brief on available RAC System Load Testing Tools and RAC System Test Plan outlines for 10gR2 & 11gR1 and
11gR2:

Document 810394.1 RAC and Oracle Clusterware Best Practices and Starter Kit (Platform Independent)

RAC Platform Specific Starter Kits and Best Practices

The following notes contain detailed platform specific best practices including Step-By-Step installation cookbooks
(downloadable in PDF format):

Document 811306.1 RAC and Oracle Clusterware Best Practices and Starter Kit (Linux)
Document 811280.1 RAC and Oracle Clusterware Best Practices and Starter Kit (Solaris)
Document 811271.1 RAC and Oracle Clusterware Best Practices and Starter Kit (Windows)
Document 811293.1 RAC and Oracle Clusterware Best Practices and Starter Kit (AIX)
Document 811303.1 RAC and Oracle Clusterware Best Practices and Starter Kit (HP-UX)

RAC on Windows Step by Step Installation Instructions

Click here for a Step By Step guide for installing Oracle RAC 10gR2 on Windows (2003 and 2008)
Click here for a Step By Step guide for installing Oracle RAC 11gR1 on Windows (2003 and 2008)
Click here for a Step By Step guide for installing Oracle RAC 11gR2 on Windows (2003 and 2008)
Click here for a Step By Step guide for installing Oracle RAC 12cR1 on Windows (2003 and 2008)

Document:2397183.1 How to Install Oracle Grid Infrastructure 12.2.0.1 on Microsoft Windows (Step-by-Step) (Doc ID
2397183.1)
Document:2575744.1 RAC on Windows: How to Install Grid Infrastructure 18c (18.1.X) on Windows (Step by Step)
(Doc ID 2575744.1)
Document:2669386.1 RAC on Windows: How to Install Grid Infrastructure 19c (19.1.X) and RAC on Windows (Step by
Step) (Doc ID 2669386.1)
Document:2871053.1 RAC on Windows: How to Install Grid Infrastructure 21c (21.3.X) and RAC on Windows (Step by
Step) (Doc ID 2871053.1)

RAC on Windows Best Practices

The Best Practices in this section are specific to the Windows Platform. Therefore, it is essential that the Platform
Independent Best Practices found in Document 810394.1 be reviewed in addition to the content provided in this
Document.

OS Configuration Considerations

Disable the Windows firewall. If the Windows firewall must be re-enabled, it MUST NOT be configured for the
private network.
Heed the list of Oracle executables that should be excluded if Firewall will be implemented. Reference:
http://docs.oracle.com/cd/E11882_01/win.112/e10845/config.htm#CEGFDJHJ
The use of Disk Encryption software on RAC servers is highly discouraged and is to be avoided as Disk encryption
software has been known to cause problems during multi-node installation and patching.
When applying OS (Windows) patches, all Oracle software should be cleanly stopped and prevented from restarting
for the duration of the patch application. For example, if patch application requires a reboot, then the
https://support.oracle.com/epmos/faces/SearchDocDisplay?_adf.ctrl-state=rknd6nmnx_4 2/8
3/28/25, 1:37 PM Document Display
OracleOHService should be set to 'Manual' until the reboot / patching is fully completed. In practical terms, all
databases should be stopped using appropriate 'srvctl stop database ...' commands, CRS should be stopped using
'crsctl stop crs' and (as previously mentioned) OracleOHService should be set to 'Manual' for the duration of
patching, then modified back to 'Automatic' once the patch(es) is / are fully applied.
Windows services for Oracle Clusterware (such as the OracleOHService) should be not be modified from their
default settings. For example, do not modify OracleOHService (or any other Oracle Clusterware related services) to
'Automatic - Delayed Start.' This causes the Service Control manager to set the priority of the initial thread for
'delayed services' to THREAD_PRIORITY_LOWEST which in turn causes all of the disk I/O performed by the thread
to be very low priority. This lowest priority for the IO can negatively impact access to the voting disks and OCR.
Inability to update the voting disks can lead to cluster evictions before the stack is fully operational. Reference:
http://blogs.technet.com/b/askperf/archive/2008/02/02/ws2008-startup-processes-and-delayed-automatic-
start.aspx
For Windows 2008 (and higher) systems modify the elevation prompt behavior for administrators to "Elevate
without prompting":
1. Open a command prompt and type 'secpol.msc' to launch the Security Policy Console
management utility.
2. From the Local Security Settings console tree, click Local Policies, and then Security
Options
3. Scroll down to and double-click User Account Control: Behavior of the elevation prompt
for administrators.
4. From the drop-down menu, select: "Elevate without prompting (tasks requesting elevation
will automatically run as elevated without prompting the administrator)"
5. Click OK to confirm the changes

Ensure that the Administrators group has the ability to manage auditing and security logs:
1. Open a command prompt and type 'secpol.msc' to launch the Security Policy Console
management utility.
2. Click on 'Local Policies'
3. Click on 'User Rights Assignment'
4. Locate and double click the 'Manage auditing and security log' in the listing of User
Rights Assignments.
5. If the Administrators group is NOT listed in the 'Local Security Settings' tab, add the
group now.
6. Click OK to save the changes (if changes were made)
Set /USEPMTIMER in the boot.ini to prevent excessive LMD and LMS trace generation and to prevent connectivity
issues as described in Document 437101.1.
Increase the size of the default Non-Interactive Desktop Heap to 2MB to prevent instability due to Desktop Heap
exhaustion. Reference: RAC on Windows: Desktop Heap Best Practice Document 2056225.1
Do not set ORACLE_HOME as an environment variable in Oracle (RAC on) Windows environments. If needed (for
example, when running opatch) set this variable as needed in a command prompt window. Reference Document
969581.1. In particular, this can cause undesired behavior (for example: listeners starting under the wrong
ORACLE_HOME) during upgrade.
Windows 2000 and 2003 systems should be optimized for Memory Usage of Programs not System Caching (not an
option in 2008):
Start -> Settings -> Control Panel -> System -> Advanced -> Performance -> Memory Usage:
Adjust for best performance of -> Programs instead of System Caching

Run Perfmon to monitor CPU, Memory, Network, Disk IO Rates - To aid in troubleshooting, configure Perfmon to
monitor these OS statistics and to generate binary log files (.BLG). Instructions for implementing this change can be
found on the Microsoft support website using the following link: http://support.microsoft.com/kb/146005

Download and install Debugging Tools for Windows (containing, among others, adplus and windbg) on each node of
your RAC on Windows cluster. These tools can be an invaluable resource when troubleshooting complex issues.
The downloads and instructions for implementation can be found on the Download and Install Debugging Tools for
Windows MSDN website.

Download and familiarize the DBA team with useful Sysinternals Windows utilities such as Process Explorer. These
utilities are available on the Microsoft Sysinternals Website.

Keep memory allocation under 80%. We recommend shooting for 75% allocated, that is, more than 20-25% free.
This will allow for ample memory needed for Windows OS operations (including collection of physical memory
dumps if required).

There is a general requirement for Oracle RAC to synchronize the time on all nodes. If the Windows Time Service is
being used, modify the Windows Time service settings to avoid large jumps in time and allow the time to gradually
match with the reference time. Restart the Windows Time service after you complete this task.
https://support.oracle.com/epmos/faces/SearchDocDisplay?_adf.ctrl-state=rknd6nmnx_4 3/8
3/28/25, 1:37 PM Document Display

1. Open a command prompt (as the Admin user) and type 'regedit'.
2. Within the registry editor locate the
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Config key.
3. Set the value for MaxPosPhaseCorrection = 600 (DECIMAL - as this is meant to represent 10
minutes)
4. Set the value for MaxNegPhaseCorrection = 600 (DECIMAL - as this is meant to represent 10
minutes)
5. Set the value for MaxAllowedPhaseOffset = 600 (DECIMAL - as this is meant to represent 10
minutes)

Be sure to run 'w32tm /config /update' after changing the settings so that the new settings
take effect.

Note that with these values set, if there is a time discrepancy between a cluster node and the
reference node that is greater than 10 minutes, time will not be adjusted and a message will
be logged (to the Windows Event Viewer)

Reference: Bug:13360724 - ENH: RAC ON WINDOWS: W32TIME REQUIREMENTS FOR ORACLE GRID
INFRASTRUCTURE
https://docs.oracle.com/cd/E11882_01/install.112/e48194/prewin.htm#CWWIN250

* Consider also setting the 'updateinterval' parameter. Reference:

http://technet.microsoft.com/en-us/library/cc773263(v=ws.10).aspx
** Consider also setting 'Maximum Tolerance for Computer Clock Synchronization' (Reference:
http://technet.microsoft.com/en-us/library/cc779260(v=WS.10).aspx). Note that Kerberos
Authentication will fail if the time difference between the nodes is greater than the 'Maximum
Tolerance for Computer Clock Synchronization'.

Note: With 11gR2, Cluster Time Synchronization Daemon (CTSSD) can be used in place of Windows Time
Service. CTSSD will synchronize time with a reference node in the cluster when Windows Time Service is
not found to be configured. Should you require synchronization from an external time source you must use
Windows Time Service which will cause CTSSD to run in "observer" mode. However, if Windows Time
Service is running, then it must to be configured as shown above.

Anti-Virus Software

Be sure to disable Anti-Virus even before downloading the installation zip files or any Oracle patch.
Disable Anti-Virus software running on cluster nodes before and for the entire duration of the installation or
patching of Oracle. (be mindful of manual reboots during this time).
Anti-Virus software may of course be re-enabled following the installation or patching, but the following should be
excluded from being scanned:

Oracle Software directories (including Oracle Home(s) and the Oracle Base)
OCFS filesystems
ACFS filesystems
Network scanning of the private interconnect

Network Considerations

A dedicated network (or VLAN) is required for private interconnect. Designate a private / separate network interface
card on each node for use as the private network. Reference: RAC on Windows: Grid Infrastructure Configuration
Step Fails at 84% (INS-20802) Document:2136803.1.
For Windows 2008 and higher, set the maxport value to a value below 61000. This will keep other processes from
using the ports that CRS processes use for communication.
cmd>netsh int ipv4 set dynamicport tcp start=49152 num=11000

Note: This puts the port range from 49152 to 60151 for Windows processes that call bind(0)

Reference: ORA-29701: Unable To Connect To Cluster Synchronization Service reported on ASM alert log in RAC on
Windows Document:2349725.1

https://support.oracle.com/epmos/faces/SearchDocDisplay?_adf.ctrl-state=rknd6nmnx_4 4/8
3/28/25, 1:37 PM Document Display
For Windows 2008 and higher, set the public network interface metric to a lower value than the private network
interface metric. Reference: RAC on Windows: Grid Infrastructure Installation Fails With OUI-35024 OR Private
Node Name is Pre-Populated into Node Selection Screen Document:1907834.1.

In Control Panel, double-click Network Connections.

Right-click a network interface, and then click Properties.
Click Internet Protocol (TCP/IP), and then click Properties.
On the General tab, click Advanced.
To specify a metric, on the IP Settings tab, click to clear the Automatic metric check box.
In the Interface Metric field, set the public network interface metric to a lower value than
the private network interface. For example, you might set the public network interface metric
to 100 and the private network interface metric to 300.

The Public network MUST be listed first in the network interface binding order.
To make this change for Windows 2008, 2012, 2012R2 perform the following:
1. Click Start, click Run, type 'ncpa.cpl', and then click OK.
2. In the menu bar on the top of the window click 'Advanced' and choose 'Advanced
Settings' (For Windows 2008, if the "Advanced" is not showing, click 'Alt' to enable
that menu item).
3. Under the Adapters and Bindings tab use the up arrow to move the Public interface
to the top of the Connections list.
4. Under Binding order for increase the priority of IPv4 over IPv6
5. Click OK to save the changes

To make this change for Windows 2016 the binding order is adjustable by setting the network interface
metric. The interface with the lower metric is 'higher' in the binding order. Reference:
https://docs.microsoft.com/en-us/windows-server/networking/technologies/network-subsystem/net-sub-
interface-metric
On Windows 2016 ensure that the metrics of Public/Private interfaces used for Grid Infrastructure are the smallest
two numbers in the list of interfaces including "Loopback Pseudo-Interface 1." Reference: Grid Infrastructure
12.2.0.1.0 Installation on Windows Server 2016 Fails Document:2327915.1

EXAMPLE:

C:\> netsh interface ipv4 set interface "Public" metric=10

C:\> netsh interface ipv4 set interface "Private" metric=30

C:\>netsh interface ipv4 show interfaces

Idx Met MTU State Name

--- ---------- ---------- ------------ ---------------------------
1 75 4294967295 connected Loopback Pseudo-Interface 1
5 10 1500 connected Public
3 30 1500 connected Private

C:\>netsh interface ipv6 show interfaces

Idx Met MTU State Name
--- ---------- ---------- ------------ ---------------------------
1 75 4294967295 connected Loopback Pseudo-Interface 1

Uncheck 'Register this connection's addresses in DNS' (Windows 2008 and higher). Reference: Grid Infrastructure
/ RAC on Windows: IP Addresses for HOST, VIP, AND SCAN Get Scrambled Upon Reboot (Doc ID 1504625.1)

By default in Windows 2008 and higher, the 'Register this connection's addresses in DNS' option is turned ON for all
network interface cards. In prior versions of windows (Windows 2000/2003 for instance) checking 'Register this
connection's addresses in DNS' (on a particular Network Interface Card (NIC)'s TCP/IP properties) only registered
the primary/first NIC ip address in DNS. In Windows 2008 checking 'Register this connection's addresses in DNS'
seems automatically registers ALL NIC ip addresses configured for that NIC. This can cause a scrambling of host,
VIP and SCAN IPs upon node reboot. Therefore, 'Register this connection's addresses in DNS' should be unchecked
for all Public NIC cards in RAC on Windows 2008 environments, as follows:

1. Invoke Server Manager

2. select 'View Network Connections'
3. select the 'public' network interface
4. choose 'Properties' from the right click menu
5. select 'Internet Protocol Version 4(TCP/IPv4)' from the 'Networking' tab
6. click 'Properties'

https://support.oracle.com/epmos/faces/SearchDocDisplay?_adf.ctrl-state=rknd6nmnx_4 5/8
3/28/25, 1:37 PM Document Display
7. click 'Advanced...' from the 'General' tab
8. select the 'DNS' tab
9. unclick the radio button for 'Register this connection's addresses in DNS'

DHCP Media Sense MUST be disabled. This change must be manually implemented for Windows 2000 but is
disabled by default in 2003. Additional information (including instructions for disabling) for Windows 2000 and
Windows 2003 can be found in MS Knowledge Base Article KB239924. For Windows 2008, this feature is once again
enabled. To disable DHCP Media Sense on 2008, execute the following from a command window as the
Administrator user:
C:\Users\Administrator> netsh interface ipv4 set global dhcpmediasense=disabled
C:\Users\Administrator> netsh interface ipv6 set global dhcpmediasense=disabled

Validate the change with:

C:\Users\Administrator> netsh interface ipv4 show global

C:\Users\Administrator> netsh interface ipv6 show global

After installing Windows Server 2003 Service Pack 2 (SP2) or higher or Windows Server 2003 or higher Scalable
Networking Pack (SNP), turn off default SNP features. On a computer that has a TCP/IP Offload-enabled network
adapter, you may experience many network-related problems like network adapters consuming lots of nonpaged
pool memory or adapters requesting large blocks of contiguous memory causing the computer to stop responding
when it tries to free the memory. This problem also affects Windows 2008 operating systems. Essentially, you can
apply this recommendation by issuing the following commands:

C:\Users\Administrator> netsh int tcp set global chimney=disabled

C:\Users\Administrator> netsh int tcp set global rss=disabled

Validate these changes with:

C:\Users\Administrator> netsh interface tcp show global

Do not use the names: PUBLIC and PRIVATE (all caps) for your public and interconnect networks (NICs) due to
unpublished Bug 6844099. The words public and private themselves may be used, for example: Public and Private
are acceptable.

Please note that IPv6 addressing is not supported with RAC for versions lower than 12c. For more information,
reference: http://www.oracle.com/technetwork/database/enterprise-edition/oracledatabaseipv6sod-2141330.pdf
and http://docs.oracle.com/database/121/CWWIN/release_changes.htm#sthref9

Network interface names in 'Network Connections' (under Control Panel\All Control Panel Items\Network
Connections) must match 'name' as indicated by 'Ethernet adapter <name>' in the ipconfig /all output.

Note that there is currently no plan to enable the Redundant Interconnect Usage feature and HAIPs on Windows.

For 11.2, the Oracle ARP protocol driver is not installed during Oracle Grid Infrastructure Installation. Install the
oraarpdrv post-GI installation as per Oracle® Database Release Notes 11g Release 2 (11.2) for Microsoft Windows.
The command: "sc query oraarpdrv" can be used to determine if the oraarpdrv is installed and running. It should
return information about the driver and be in the state "Running". If the oraarpdrv is not running, it can be started
using the command: "sc start oraarpdrv" or rebooting the node.

Storage Considerations

It is strongly advised to bring the entire Oracle software stack down in order to complete all disk virus scans for
conventional Fat 16/32/NTFFS as well as OCFS file systems. This is because Oracle and the virus scan software use
different types of locking which are not compatible. Hence a shared disk for the database configured with OCFS
could have 2 nodes virus scanning at the same time and could potentially cause the cluster to crash. We strongly
suggest that you virus scan only from one node and only during maintenance windows. OCFS disks that only
contain Oracle database datafiles do not need to be virus scanned. OCFS disks that contain any non-database
datafiles or database configuration files should be scanned periodically (with the entire Oracle stack down).

Desupport of the Oracle Cluster File System (OCFS) on Windows is final with Oracle Database 12. Customers
currently using OCFS on Windows to host either the Oracle cluster files (Oracle Cluster Registry - OCR - and Voting
Files) or database files or both will need to migrate these files off OCFS prior to upgrading to Oracle Database 12.
See My Oracle Support Document 1392280.1 for more details.

Hardware/Vendor Specific Considerations

https://support.oracle.com/epmos/faces/SearchDocDisplay?_adf.ctrl-state=rknd6nmnx_4 6/8
3/28/25, 1:37 PM Document Display
Ensure minimum BIOS version 2.35.3.3 is used for SUN V40Z DUAL CORE machines, for ECC memory checking.
Ensure SUN V40Z 2.6V memory management voltage regulator issues. A SUN CE can identify if the voltage
regulator is beginning to fail. The new VRM (Voltage Regulator Module) revision board from rev 1.0 to rev 2.0.

Oracle Software Considerations

The Software Considerations in this section are specific to the Windows Platform. That said, it is highly recommended
that the Platform Independent Best Practices found in Document 810394.1 be reviewed in addition to the content
below.

Installation and Upgrade and Patching

Verify the installation user is configured to update the Windows registry on each node in the cluster:
Run regedit from the Run menu or the command prompt.
From the File menu select Connect Network Registry.
In the 'Enter the object name…' edit box enter the name of a remote node in the
cluster, then click OK.
Wait for the node to appear in the registry tree.

If the remote node does not appear in the registry tree or you are prompted to fill in a
username and password, then you must resolve the permissions issue at the operating system
level before proceeding with the Oracle Grid Infrastructure installation.

NOTE: Along with this you may also need to (re)start "Remote Registry" Service in Windows
Services (services.msc) and set it to Automatic on all cluster nodes

While ORACLE_HOME should never be set as a system environment variable for any Oracle on Windows
environment, in particular do not set ORACLE_HOME set (to any value) during an upgrade will cause many and
diverse issues.
Ensure that 'Register this connection's addresses in DNS' is UNCHECKED for all network adapter's IPv4 properties,
otherwise DNS may get wrong entries for resolving Oracle VIP hostname
'User Account Control: Turn On Admin Approval Mode' should be DISABLED on all nodes under 'Administrative Tools
-> Local Security Policy -> Security Options. This will ensure that the Grid Infrastructure upgrade succeeds in
propagating to remote nodes
Read through the Release Notes before beginning any 11gR2 Grid Infrastructure installation. In particular, be sure
to install the Oracle ARP Protocol Driver. Reference:
http://docs.oracle.com/cd/E11882_01/relnotes.112/e23557/toc.htm#CJAHFJGC. Note that the Oracle ARP Protocol
Driver should be re-installed following a Grid Infrastructure upgrade (such as from 11.2.0.2 to 11.2.0.3).
Install both Grid Infrastructure software and RDBMS software under 'generic' usernames. Note that elimination of a
software owner username will require a reinstall of Oracle software.
Prevent installation failures by disabling the Windows Firewall prior to installation of Oracle, this applies to all Oracle
versions. See the OS Configuration Considerations section within this note for details.
When patching Grid Infrastructure 11.2.0.4 and higher, 'Windows Management Instrumentation' (WMI) services on
each node should remain STARTED and ENABLED on each node while patching.
When patching Grid Infrastructure 11.2.0.3 and lower, 'Windows Management Instrumentation' (WMI) services on
each node should be stopped and disabled on each node while patching. Specifically just prior to 'opatch apply -
local'. WMI services should be re-enabled on each node following successful patching via 'opatch apply -local'
'Distributed Transaction Coordinator' (MSDTC) should be stopped on each node prior to installation or upgrade or
patching.
Prepare for resolution of potential locked file issues by downloading 'Process Explorer' from Microsoft's sysinternals
website prior to installation or patching.

General

Be sure that the latest windows bundle patch has been applied to ensure optimal performance and stability of the
system. This applies to ALL Oracle releases. The latest available patch bundles can be found in Document
161549.1.

Note that as a normal function of our Oracle Clusterware / Grid Infrastructure, OraFenceService is designed to fence
(I/O) and reboot a node if it perceives that that node is 'hung' once its configured timeout has been reached. The
default timeout for the OraFence driver is a (very low) 5 seconds. What this means is that if the OraFence driver
detects what it perceives to be a hang at the operating system level and that hang persists beyond 5 seconds, it's
possible that the OraFence driver - of its own accord - will fence and evict the node. It is advisable in some cases
to increase the OraFence timeout value as high as 16 (decimal) seconds in some cases. The OraFence timeout is
https://support.oracle.com/epmos/faces/SearchDocDisplay?_adf.ctrl-state=rknd6nmnx_4 7/8
3/28/25, 1:37 PM Document Display
controlled by the following Windows registry key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\OraFenceService\Timeout. Note that modification of
the OraFenceService timeout value requires a node reboot. Reference the following My Oracle Support document
for more information on correctly setting this Timeout (and associated registry key): RAC on Windows: How To
Correctly Increase the OraFenceService Timeout Value (and avoid: 'OraFence driver has not been scheduled in the
WarningTimeout period') Document 2339930.1

Community Discussions

Still have questions? Use the communities link below to search for similar discussions or start a new discussion on this
subject.

Click here to open in main browser window.

REFERENCES

NOTE:810394.1 - RAC and Oracle Clusterware Best Practices and Starter Kit (Platform Independent)

NOTE:811280.1 - RAC and Oracle Clusterware Best Practices and Starter Kit (Solaris)
NOTE:811303.1 - RAC and Oracle Clusterware Best Practices and Starter Kit (HP-UX)

NOTE:744125.1 - Windows: Connections Fail with ORA-12640 or ORA-21561

BUG:13360724 - ENH: RAC ON WINDOWS: W32TIME REQUIREMENTS FOR ORACLE GRID INFRASTRUCTURE

NOTE:1392280.1 - Desupport of Oracle Cluster File System (OCFS) on Windows with Oracle Database 12

NOTE:969581.1 - How to Set or Switch Oracle Homes on Windows

NOTE:2871053.1 - RAC on Windows: How to Install Grid Infrastructure 21c (21.3.X) and RAC on Windows (Step by Step)
Didn't find what you are looking for?

https://support.oracle.com/epmos/faces/SearchDocDisplay?_adf.ctrl-state=rknd6nmnx_4 8/8