Manualshelf

Owner's Manual

ManualsBrandsDell ManualsSoftwareDell Oracle Database 10g Enterprise Edition - Microsoft Windows Server 2003
11121314151617181920
Deployment Guide 11
• Each node must have the following software installed:
– Windows Server 2003, Enterprise x64 Edition with SP1 (see Table 1-1)
– HBA driver
• The Fibre Channel storage must be configured with the following:
– A minimum of three LUNs created and assigned to the cluster
– A minimum LUN size of 40 GB (for one LUN) and 1 GB (for two LUNs)
Cabling Your Storage System for a SAN-Attached Configuration
Use the following procedure to configure your Oracle Cluster storage system in a four port SAN-attached
configuration.
1
Connect one optical cable from SP-A port 0 to Fibre Channel switch 0.
2
Connect one optical cable from SP-A port 1 to Fibre Channel switch 1.
3
Connect one optical cable from SP-B port 0 to Fibre Channel switch 1.
4
Connect one optical cable from SP-B port 1 to Fibre Channel switch 0.
5
Connect one optical cable from HBA0 on node 1 to Fibre Channel switch 0.
6
Connect one optical cable from HBA1 on node 1 to Fibre Channel switch 1.
7
Connect one optical cable from HBA0 of each additional node to Fibre Channel switch 0.
8
Connect one optical cable from HBA1 of each additional node to Fibre Channel switch 1.
Configuring Networking and Storage for Oracle RAC 10g R2
This section provides information about setting up a Fibre Channel cluster and includes the following
procedures:
• Configuring the public and private networks
• Verifying the storage configuration
• Configuring shared storage for Oracle Clusterware and the Oracle database
NOTE: Oracle RAC 10g R2 is a complex database configuration that requires an ordered list of procedures. To
configure networking and storage in a minimal amount of time, perform the following procedures in order.
Configuring the Public and Private Networks
NOTE: Each node requires a unique public and private IP address and an additional public IP address to serve as
the virtual IP address for the client connections and connection failover. The virtual IP address must belong to the
same subnet as the public IP address. All public IP addresses, including the virtual IP address, should be registered
with DNS.