Installation of ORACLE 12C Grid Infrastructure Cluster on Windows 2012 R2:
Upon research and reading I found that before we proceed for installing ORACLE GRID 12c on Windows Environment, we need to ensure that the following perquisites are meet:
Step 1 :
Information about the TCP
Chimney Offload, Receive Side Scaling, and Network Direct Memory Access
features
netsh int tcp show global
netsh int tcp set global chimney=disabled
netsh int tcp set global rss=disabled
netsh int tcp show global
Step 2 :
Disabling Windows
Media SensingDisabling Windows
Media Sensing
Windows Media Sensing must be disabled for the private network adapters.
Windows Media Sensing must be disabled for the private network adapters.
To
disable Windows Media Sensing for TCP/IP, you must set the value of the DisableDHCPMediaSense parameter to 1 on each node. Because you must modify the
Windows registry to disable Media Sensing, you should first backup the registry
and confirm that you can restore it, using the methods described in your
Windows documentation.
- Backup the Windows registry.
- Use Registry Editor to view the
following key in the registry:
3.
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Tcpip\Parameters
- Add a new DWORD value to the
Parameters subkey:
5.
Value Name: DisableDHCPMediaSense
6.
Value: 1
- Exit the Registry Editor and
restart the computer.
- Repeat steps 1 through 4 on
each node in your cluster.
Step 3:
Setting the Bind Order for Network Adapters
Setting the Bind Order for Network Adapters
In Windows Networking Properties, the public network connection
on each node must be listed first in the bind order (the order in which network
services access the node). The private network connection should be listed
second.
1. Right click My Network Places and choose Properties.
2. Click Alt to see the Advance Menu
3. In the Advanced menu, click Advanced Settings.
4. If the public network connection name
is not the first name listed under the Adapters and Bindings tab, then select
it and click the arrow to move it to the top of the list.
5. Click OK to save the settings and then exit the
network setup dialog.
The names used for each class of network adapter (such as
public) must be consistent across all nodes. You can use nondefault names for
the network adapter, for example,
PublicLAN, if the same names are used
for the same class of network adapters on each node in the network.
Step 4 :
Manually Configure Automatic Metric Values
Automatic Metric is a new feature for Windows Server 2012 that
automatically configures the metric for the local routes that are based on link
speed. To prevent OUI from selecting the wrong network interface during
installation, you must customize the metric values for the public and private
network interfaces on Windows Server 2012 and Windows Server 2012 R2 systems.
The Automatic Metric feature is enabled by default, and it can
also be manually configured to assign a specific metric. On Windows Server
2012, the public and private network interface for IPv4 use the Automatic
Metric feature of Windows. When the Automatic Metric feature is enabled and
using the default values, it can sometimes cause OUI to select the private
network interface as the default public host name for the server when
installing Oracle Grid Infrastructure.
1. In Control Panel, double-click Network
Connections.
2. Right-click a network interface, and then
click Properties.
3. Click Internet
Protocol (TCP/IP), and then click Properties.
4. On the General tab, click Advanced.
5. To specify a metric, on the IP
Settings tab, click to clear the Automatic metric check box.
6. 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 100and
the private network interface metric to 300.
Step 5 :
Set the Dynamic Port Range for Oracle RAC Installations
For certain configurations of Oracle RAC in high load
environments it is possible for the system to exhaust the available number of
sockets. To avoid this problem, expand the dynamic port range for TCP/IP.
1.
Open
a command line window as an Administrator user.
2.
Run
the following command:
netsh int ipv4 set dynamicport tcp start=20000 num=40000
Step
6:
Deconfigure DNS Registration for Public Network Adapter
To prevent Windows Server 2008 from potentially registering the
wrong IP addresses for the node in DNS after a server restart, you must
deconfigure the "Register this connection's addresses in DNS" option
for the public network adapters.
Due to a change in functionality in the Windows Server 2008
operating system, the DNS client service registers all of the network
connections of a computer in DNS. In earlier versions of Windows Server, only
the DNS client service registered only the primary, or first, network adapter
IP address in DNS.
1. Start the Windows Server Manager
application.
2. Select View Network
Connections.
3. Right-click the network adapter that
provides the Public network interface and select Properties.
4. Select the Networking tab, and then
select Internet
Protocol Version 4 (TCP/IPv4).
Note: If you configure this setting in IPv4, then Windows
automatically configures the same setting for IPv6.
5. Click Properties.
6. On the General tab, click Advanced.
7. Select the DNS tab.
8. Deselect Register this
connection's addresses in DNS.
Step 7 :
Verify Privileges for Copying Files in the Cluster
During installation, OUI copies the software from the local node
to the remote nodes in the cluster. Verify that you have Administrator
privileges on the other nodes in the cluster by running the following command
on each node, where nodename is the
name of the remote node:
net use \\nodename\C$
After installation, if your system does not use the net share
shown in the above example, then you can remove the unused net share using the
following command:
net use \\nodename\C$ /delete
net use \\nodename\C$ /delete
