In Progress
About
RAC Installation
Network
The two nodes in the cluster must be able to communicate with each other and with external clients using the TCP/IP protocol. Communication between clients and the nodes in the cluster is across the public network. Both nodes need a network adapter configured for the public network.
To enable availability and failover, a virtual IP (VIP) address is also required for each of your nodes. A VIP address can be moved between nodes in case of a failure. CRS manages the VIP addresses for you.
To support a virtual IP address, both nodes require an unused IP address that is compatible with the public network's subnet and netmask. The virtual IP address and host name should also be registered in the domain name system (DNS).
For communication between the instances running on the two nodes, a private network is required. This private network connects only the nodes in the cluster and cannot be accessed from outside the cluster. Both nodes need a separate network adapter configured for this private network.
Public Versus Private Network
Both nodes must meet the following public and private network requirements:
1. Support for two network adapters
Public network interface used for client connections
Private network interfaces used for communication between database instances
2. Support of interface name restrictions
Names are case sensitive.
Names must not contain any multibyte language characters.
Public and private network interface names must be different from each other.
Names for each interface must be the same on both nodes.
Public and private IP addresses must be on different subnets.
3. An IP address and host name registered in the domain name system (DNS) for the public network interface
4. A private IP address and optionally, a private host name, for each private network interface
Note: Oracle recommends that you use private network IP addresses for these interfaces, for example: 10.*.*.* or 192.168.*.*. You can use a %SystemRoot%\system32\drivers\etc\hosts file on both nodes to associate private host names with private IP addresses.
| Host Name | Type | IP Address | Registered In |
|---|---|---|---|
| iwinrca01.us.oracle.com | Public | 139.185.150.201 | DNS |
| iwinrca02.us.oracle.com | Public | 139.185.150.202 | DNS |
| viprca01.us.oracle.com | Virtual | 139.185.150.54 | DNS |
| viprca02.us.oracle.com | Virtual | 139.185.150.55 | DNS |
| iwinrca01-node | Private | 10.10.10.2 | Hosts file |
| iwinrca02-node | Private | 10.10.10.3 | Hosts file |
Ensure the public interface is first in the bind order:
- Open the “Network Connections” dialog by right-clicking on the “My Network Places” icon and selecting the “Properties” menu option.
- Select the “Advanced > Advanced Settings…” menu option.
- On the “Adapters and Bindings” tab, make sure the public interface is the first interface listed.
- Accept any modifications by clicking on the “OK” button and exiting the “Network Connections” dialog.
Network Adaptater
VMware sometimes creates additional network adapters, which will prevent the clusterware from loading. Delete any additional adapters as follows. Open a command prompt and issue the following commands.
set devmgr_show_nonpresent_devices=1
devmgmt.msc
How to disable the Media Sensing feature for TCP/IP in Windows
On a Windows-based computer that uses TCP/IP, you can use the Media Sensing feature to detect whether the network media are in a link state. Ethernet network adapters and hubs typically have a “link” light that indicates the connection status. This status is the same condition that Windows interprets as a link state. Whenever Windows detects a “down” state, it removes the bound protocols from that adapter until it is detected as “up” again. Sometimes, you may not want the network adapter to detect this state. You can set this configuration by modifying the registry.
Preinstallation Step for Windows Server 2003
http://download.oracle.com/docs/html/B10132_04/toc.htm#BABHFHGA To use raw partitions or logical drives on Windows Server 2003, you must enable disk automounting. Enable disk automounting for:
- Raw Partitions for Oracle Real Application Clusters (RAC)
- Cluster File System for Oracle Real Application Clusters
- Oracle Clusterware
- Raw partitions for a single-node database
- Logical drives for Automatic Storage Management (ASM)
Follow these steps to enable automounting:
- Enter the following commands at a command prompt:
C:\> diskpart
DISKPART> automount enable
DISKPART> exit
- Restart your computer.
A Description of the Diskpart Command-Line Utility
You can use this utility to enable storage configuration from a script, a remote session, or another command prompt. Diskpart enhances the Disk Administrator graphical user interface (GUI).
Vmx configuration File
To support disk sharing, you must change some configuration in the ini file from the virtual Machine. Edit the contents of the vmx file using a text editor,
disk.locking = "FALSE"
diskLib.dataCacheMaxSize = "0"
diskLib.dataCacheMaxReadAheadSize = "0"
diskLib.dataCacheMinReadAheadSize = "0"
diskLib.dataCachePageSize = "4096"
diskLib.maxUnsyncedWrites = "0"
scsi1.present = "TRUE"
scsi1.virtualDev = "lsilogic"
scsi1.sharedBus = "VIRTUAL"
scsi1:1.present = "TRUE"
scsi1:1.mode = "independent-persistent"
scsi1:1.fileName = "/u01/VM/shared/ocr.vmdk"
scsi1:1.deviceType = "plainDisk"
scsi1:1.redo = ""
scsi1:2.present = "TRUE"
scsi1:2.mode = "independent-persistent"
scsi1:2.fileName = "/u01/VM/shared/votingdisk.vmdk"
scsi1:2.deviceType = "plainDisk"
scsi1:2.redo = ""
scsi1:3.present = "TRUE"
scsi1:3.mode = "independent-persistent"
scsi1:3.fileName = "/u01/VM/shared/asm1.vmdk"
scsi1:3.deviceType = "plainDisk"
scsi1:3.redo = ""
scsi1:4.present = "TRUE"
scsi1:4.mode = "independent-persistent"
scsi1:4.fileName = "/u01/VM/shared/asm2.vmdk"
scsi1:4.deviceType = "plainDisk"
scsi1:4.redo = ""
scsi1:5.present = "TRUE"
scsi1:5.mode = "independent-persistent"
scsi1:5.fileName = "/u01/VM/shared/asm3.vmdk"
scsi1:5.deviceType = "plainDisk"
scsi1:5.redo = ""