Академический Документы
Профессиональный Документы
Культура Документы
2)
System Requirements
Tmp
Ensure that you have at least 4 GB of space in /tmp.
Network Requirements
Each node must have at least two network adapters or network interface cards (NICs): one
for the public network interface, and one for the private network interface (the
interconnect).
For the public network, each network adapter must support TCP/IP.
For the private network, the interface must support the user datagram protocol (UDP)
using high-speed network adapters and switches that support TCP/IP (minimum
requirement 1 Gigabit Ethernet).
Private interfaces for interconnects must be on the same subnet, and that subnet must
connect to every node of the cluster. For example, if the private interfaces have a subnet
mask of 255.255.255.0, then your private network is in the range 192.168.0.0--
192.168.0.255, and your private addresses must be in the range of 192.168.0.[0-255]. If
the private interfaces have a subnet mask of 255.255.0.0, then your private addresses can
be in the range of 192.168.[0-255].[0-255].
Software Requirements List for Solaris Operating System (x86 64-Bit) Platforms
Item Requirement
Operating system
Solaris 10
SUNWarc
SUNWbtool
SUNWcsl
SUNWhea
SUNWlibC
SUNWlibm
SUNWlibms
SUNWsprot
SUNWtoo
SUNWi1of (ISO8859-1)
SUNWi1cs (ISO8859-15)
SUNWi15cs
SUNWxwfnt
119961-05 or later
119964-14 or later
120754-06 or later
139556-08 or later
139575-03 or later
141415-04 or later
141445-09 or later [11.2.0.2]
140797-01
140900-01
141017-01
141415-10
141737-05
RAC Installation
SSH
Permit SSH connections on all cluster member nodes for the user account that will own the Oracle RAC
installation
Single Client Access Name (SCAN): A domain name that resolves to all the addresses
allocated for the SCAN. Oracle recommends that you allocate three addresses to the SCAN.
During Oracle Grid Infrastructure installation, listeners are created for each of the SCAN
addresses, and Oracle Clusterware controls which server responds to a SCAN address request.
For high availability, you should provide at least three IP addresses in the DNS to use for SCAN
mapping. A SCAN domain name must be unique within your corporate network.
Virtual IP address: A public internet protocol (IP) address for each node, to be used as the
Virtual IP address (VIP) for client connections. If a node fails, then Oracle Clusterware fails over
the VIP address to an available node.
During installation, if you do not use Grid Naming Service (which provides the VIP
automatically), then you provide VIP addresses. The VIP for each node is associated with the
same interface name on every node that is part of your cluster. If you have a domain name server
(DNS), then your network administrator should register the host names for the VIP with the DNS,
so that the DNS is resolvable from any client, as well as the cluster nodes. The VIP should not be
in use at the time of the installation, because this is an IP address that Oracle Clusterware
manages.
Public IP address: A public host name address for each node, assigned by GNS, or assigned by
the system administrator during initial system configuration for manual configurations. The
public IP address name must be resolvable to the hostname. Register both the public IP and the
VIP address with the DNS. If you do not have a DNS, then you must make sure that both public
IP addresses are in the node /etc/hosts file (for all cluster nodes).
Private IP address: A private IP address for each node to serve as the private interconnect
address, dedicated exclusively to internode cluster communication. GNS configures the address
automatically. If you select manual configuration, then you must ensure that the following is true
for each private IP address. The private IP address must be:
The private interconnect is used for internode communication by both Oracle Clusterware and
Oracle RAC. If you use manual configuration, then the private IP address must be available in
each node's /etc/hosts file. Oracle recommends that the private network interconnects ar
configured on dedicated switches that are not connected to anything other than the nodes in the
same cluster.
Address
Home Given Assigned Resolved
Identity Node Host Node Name Type Address By By
Node 1 Node 1 node1 node1Foot 1 Public 192.0.2.101 Fixed DNS
Public
Node 1 Node 1 Selected by node1-vip Virtual 192.0.2.104 Fixed DNS and
VIP Oracle hosts file
Clusterware
Node 1 Node 1 node1 node1-priv Private 192.168.0.1 Fixed DNS and
Private hosts file, or
none
Node 2 Node 2 node2 node2Footref 1 Public 192.0.2.102 Fixed DNS
Public
Node 2 Node 2 Selected by node2-vip Virtual 192.0.2.105 Fixed DNS and
VIP Oracle hosts file
Clusterware
Node 2 Node 2 node2 node2-priv Private 192.168.0.2 Fixed DNS and
Private hosts file, or
none
SCAN none Selected by mycluster- virtual 192.0.2.201 Fixed DNS
VIP 1 Oracle scan
Address
Home Given Assigned Resolved
Identity Node Host Node Name Type Address By By
Clusterware
SCAN none Selected by mycluster- virtual 192.0.2.202 Fixed DNS
VIP 2 Oracle scan
Clusterware
SCAN none Selected by mycluster- virtual 192.0.2.203 Fixed DNS
VIP 3 Oracle scan
Clusterware
Shell Limits