|Oracle® Clusterware Installation Guide
11g Release 1 (11.1) for Microsoft Windows
|PDF · Mobi · ePub|
The following is a summary of the installation configuration requirements and commands. This summary is intended to provide an overview of the installation process.
In addition to providing a summary of the Oracle Clusterware installation process, this list also contains configuration information for preparing a system for Automatic Storage Management (ASM) and Oracle Real Application Clusters (Oracle RAC) installation.
For more information, review "Checking Hardware Requirements".
In the Windows Task Manager window, select the Performance tab to view the available memory for your system.
To view the Virtual memory settings, from the Control panel, select System. In the System Properties window, select the Advanced tab, then, under Performance, click Performance Options. In the Performance Options window, the virtual memory, or page file, settings are displayed at the bottom of the window.
The minimum required RAM is 1 GB, and the minimum required swap space is 1 GB. Oracle recommends that you set the paging file size to twice the amount of RAM for systems with 2 GB of RAM or less. For systems with 2 GB to 8 GB RAM, use a paging file size equal to RAM. For systems with over 8 GB RAM, use .75 times the size of RAM for the paging file size.
From the Control Panel, select Administrative Tools, then select Computer Management. In the menu on the left-hand side of the Computer Management window, under Storage, select Disk Management.
The Disk Management window displays the available space on file systems. If you use standard redundancy for Oracle Clusterware files, which is 2 Oracle Cluster Registry (OCR) partitions and 3 voting disk partitions, then you should have at least 1 GB of disk space available on separate physical disks reserved for Oracle Clusterware files. Each Oracle Clusterware file should be at least 256 MB in size.
Note:When you create partitions by specifying a size for the partition, such as 256 MB, the actual size of the created partition may be smaller than the size requested, based on the cylinder geometry of the disk. Oracle configuration software checks that the devices being used for Oracle Clusterware files contain a minimum of 256 MB of available disk space, not total disk space. Therefore, Oracle recommends using at least 280MB for the device size, to ensure there is 256 MB of available disk space.
The Oracle Clusterware home requires 650 MB of disk space.
Ensure that you have at least 400 MB of disk space in the Windows TEMP directory. If this space is not available, then increase the partition size, or delete unnecessary files in the TEMP directory. Make sure the environment variables
TMP both point to the location of the TEMP directory, for example:
For more information, review "Checking Network Requirements".
The following is a list of address requirements that you must configure on a domain name server (DNS), or configure in the
%SystemRoot%\system32\drivers\etc\hosts file for each cluster node:
You must have three network addresses for each node:
A public internet protocol (IP) address
A virtual IP (VIP) address, which is used by applications for failover in the event of node failure
A private IP address, which is used by Oracle Clusterware and Oracle RAC for internode communication
The virtual IP address has the following requirements:
The IP address and host name are currently unused (it can be registered in a DNS, but should not be accessible by a ping command)
The virtual IP address is on the same subnet as your public interface
The private IP address has the following requirements:
It should be on a subnet reserved for private networks, such as 10.0.0.0 or 192.168.0.0
It should use dedicated switches or a physically separate, private network, reachable only by the cluster member nodes, preferably using high-speed NICs
It must use the same private interfaces for both Oracle Clusterware and Oracle RAC private IP addresses
It cannot be registered on the same subnet that is registered to a public IP address
After you obtain the IP addresses from a network administrator, to assign the public and private IP addresses to NICs, right-click on My Network Places and select Properties. In the Network and Dial-up Connections window, right-click the device for which you want to change the IP address, and select Properties. Select Internet Protocol (TCP/IP), then click Properties. Do not assign the VIP address.
Ensure that the public (external) host names are defined in your DNS and that the correct IP addresses resolve for all nodes in the cluster. Ensure that all public (external) and private (internal) host names are defined in the hosts file on all nodes of the cluster. Test your cluster configuration by pinging all host names from each node and check for proper names resolution. The public and private IP addresses should respond to
ping commands. The VIP addresses should not respond.
Check the network adaptor binding order on each node. Ensure that your public network adaptor is first in the bind order, and the private network adaptor is second. Follow these steps to configure the network adaptor bind order:
Right-click My Network Places and choose Properties.
In the Advanced menu, click Advanced Settings.
If the public interface 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 list.
Increase the priority of IPv4 over IPv6.
Click OK to save the setting and then exit the network setup dialog.
The names used for each class of network adaptor (such as public) must be consistent across all nodes. You can use nondefault names for the network adaptors, for example, PublicLAN, as long as the same names are used for the same class of network adaptors on each node in the network.
Media Sense allows Windows to uncouple an IP address from a network adaptor when the link to the local switch is lost. To disable Windows Media Sensing for TCP/IP, you must set the value of the
DisableDHCPMediaSense parameter to 1 on each node. Because you need to 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. Disable Media Sensing by completing the following steps on each node of your cluster:
Backup the Windows registry.
Use Registry Editor (
Regedt32.exe) to view the following key in the registry:
Add the following registry value:
Value Name: DisableDHCPMediaSense Data Type: REG_DWORD -Boolean Value: 1
Restart the computer.
During installation, OUI copies the software from the local node to the remote nodes in the cluster. Verify that you have administrative privileges on the other nodes in the cluster by running the following command on each node, where
nodename is the node name:
net use \\nodename\C$
For this example, assume that you have one Oracle installation owner, and that this Oracle installation software owner name is
oracle. The oracle user must be either a local Administrator user or a domain user, and the same user must exist (same user name, password, and domain) on each node in the cluster. If you use a domain user, then the user on each node must be in the same domain. For example, you cannot have a
dba1 user on the first node in the
DBADMIN domain and a
dba1 user on the second node in the
Tip:For more information, review the section "Configuring User Accounts".
To install properly across all nodes, the Oracle Universal Installer will need to use the temporary folders defined within Microsoft Windows. The TEMP and TMP folders should be the same across all nodes in the cluster. By default, these settings are defined as
%USERPROFILE%\Local Settings\Temp and
%USERPROFILE%\Local Settings\Tmp in the Environment Settings of My Computer. It is recommended to explicitly redefine these as
WIN_DRIVE:\tmp, for example,
C:\tmp for all nodes, if Windows is installed on the C drive.
For installations with Oracle Clusterware only, Oracle recommends that you let Oracle Universal Installer (OUI) create the Oracle Clusterware and Oracle Central Inventory (
oraInventory) directories for you. However, as
Administrator, you must create a path compliant with Oracle Optimal Flexible Architecture (OFA) guidelines, so that OUI can select that directory during installation. For OUI to recognize the path as an Oracle software path, it must be in the form C:\... .
Oracle RAC requires that each node be able to access a set of files on a shared disk subsystem. All instances in the cluster share these files.
The following sections outline the procedure for creating OCR and voting disk partitions, and preparing ASM disks.
For additional information, review the following sections:
The following steps outline the procedure for creating an OCR and voting disk partition:
Run Windows Disk Management from one node to create an extended partition. Use a basic disk: dynamic disks are not supported.
If you plan to store the Oracle Clusterware binaries on OCFS, create at least two logical partitions: one for the Oracle Clusterware home and one for the Oracle Clusterware files. You do not need to create separate partitions for the OCR and voting disk if you plan to use OCFS. OCFS creates individual files for the OCR and voting disk.
If your file system does not use RAID, then create an extended partition and logical partition for each additional file system or disk drive that will be used by Oracle Clusterware.
To create the required partitions, use the Disk Management utilities available with Microsoft Windows. Use a basic disk with a Master Boot Record (MBR) partition style as an extended partition for creating partitions.
From one of the existing nodes of the cluster, run the Windows disk administration tool as follows:
Click Start, then select Settings, Control Panel, Administrative Tools, and then Computer Management
Expand the Storage folder to Disk Management. Use a basic disk with a Master Boot Record (MBR) partition style as an extended partition for creating partitions. Right click inside an unallocated part of an extended partition and choose Create Logical Drive.
If using OCFS, specify a size for the partition that is at least 520 MB to store both the OCR and voting disk, or a size of 500 MB (the minimum size) to store just the voting disk or OCR. If using raw devices, then specify a size that is at least 280 MB to store a single OCR or voting disk file.
When specifying options for the logical drive, choose the option "Do not assign a drive letter or path" and "Do not format this partition". Repeat these steps to create enough partitions to store all the required files.
Repeat Step 1 to create all the required partitions.
If you are preparing drives on a Windows 2003 system, then you should restart all nodes in the cluster after you have created the logical drives.
Check all nodes in the cluster to ensure that the partitions are visible on all the nodes and to ensure that none of the Oracle partitions have drive letters assigned. If any partitions have drive letters assigned, then remove them by performing these steps:
Right-click the partition in the Windows disk administration tool
Select "Change Drive Letters and Paths..." from the menu
Click Remove in the "Change Drive Letter and Paths" window
Use Microsoft Computer Management utility or the command line tool
diskpart to create the partitions. Ensure that you create the partitions without drive letters. After you have created the partitions, the disks must be stamped with a header.
If you install Oracle Database in interactive mode, then Oracle Universal Installer configures the disks' headers during the installation process. If you plan to install Oracle Database in noninteractive mode, then you need to configure the disks manually before installation either by using
asmtoolg (GUI version) or using
asmtool (command line version).
For more information on configuring your disks with
asmtoolg, refer to the section "Using asmtoolg (Graphical User Interface)". To configure the disks with
asmtool, refer to the section "Using asmtool (Command Line)".
For information, review the following section in "Verifying Oracle Clusterware Requirements with CVU".
Using the following command syntax, log in as the administrative user, and start Cluster Verification Utility (CVU) to check system requirements prior to installing Oracle Clusterware. In the following syntax example, replace the variable
mountpoint with the path to the installation media, and replace the variable
node_list with the names of the nodes in your cluster, separated by commas:
mountpoint\runcluvfy.bat stage -pre crsinst -n node_list
For example, if you want to verify the system requirements have been met for
node2, and your installation media is available on drive
F:, then enter the following command:
F:\runcluvfy.bat stage -pre crsinst -n node1,node2
For information, review the following sections in"Verifying Oracle Clusterware Requirements with CVU" AND "Installing Oracle Clusterware with OUI".
Navigate to the installation media, and start OUI. For example, if the installation media is available on drive D:, you would use the following commands:
cd D:\Disk1 setup.exe
Select Install Oracle Clusterware, and enter the configuration information as prompted.
After you have installed Oracle Clusterware, apply any available patch sets.