RAC 9i Install steps:
- OS installation
- Created Volume Groups and logical volumes
- Configured Clusters ( here it’s hp Service Guard)
- Start Cluster
- Install Oracle RAC (aka OPS) version
In both the nodes:
- Configure lan0 as primary lan
- Configure lan1 for dedicated heartbeat
For simplicity, keep the IP addresses consistent on each node. For example, if the primary lan is 126.96.36.199, use 188.8.131.52 as secondary lan ip address. Configure lan2 for standby lan
- Connect a lan card on port 2 between two nodes. Do not assign an ip address.
10g RAC Install steps:
Public interface that will be used for client communication (For public network each network adapter must support TCP/IP)
l Virtual IP address (VIP) that will be bind by Oracle Clusterware to the public interface
- VIP should be on the same subnet as the public interface
- VIP should be registered in DNS or maintained in /etc/hosts with the associated network name.
- VIP feature works at a low level with the device files for the network interface cards, and as a result might clash with any other SG/ Vendor Relocatable IP addresses also configured for the same public NIC. Therefore, it has not been supported to configure the public NIC used for Oracle VIP also for any other SG Relocatable IP address.
l Private interface for inter-cluster traffic.
Below are the major categories of inter-cluster traffic when no third party clusterware or clustered FS is not present:
a) CSS-HB = Oracle CSS heartbeat traffic and communications traffic for Oracle
Clusterware. CSS-HB uses a single logical connection over a single subnet network.
b) RAC-IC = RAC instance peer to peer traffic and communications for Global Cache
c) Service (GCS) and
d) Global Enqueue Service (GES), formally Cache Fusion (CF) and
e) Distributed Lock Manager (DLM).
Considerations for Private N/W:
- The interconnect must support UDP as this is the default interconnect protocol for cache fusion
- TCP is the interconnect protocol for Oracle Clusterware.
- Crossover cables are not supported for the cluster interconnect; switch is mandatory for production implementation, even for only 2 nodes architecture.
- In some cases it might not be possible to place all interconnect traffic on the
- same network. For example if RAC-IC traffic is very high, so that a separate network for RAC-IC may be needed.
11gR2 RAC Install steps:
RAC on 11gR2 is same as 10gR2 apart from the SCAN IP.
The Cluster scan address must be on the same subnet as the public interface.
Cluster scan address and Cluster scan host name must be currently unused (it can be registered in a DNS, but should not be accessible by a ping command).
The SCAN should be resolved in DNS and have 3 IP addresses assigned using round robin load balancing.