5 Installing Oracle Clusterware

This chapter describes the procedures for installing Oracle Clusterware on Windows-based systems. The topics in this chapter are:

Note:

If you are going to install Oracle Real Application Clusters, then this chapter describes phase one of the Oracle Database 11g Real Application Clusters (Oracle RAC) installation, the Oracle Clusterware installation. The second phase of an Oracle RAC installation, installing Oracle RAC, is described in Oracle Real Application Clusters Installation Guide for Microsoft Windows.

Note:

To install Oracle Clusterware on Windows Server 2008, use the Oracle Database 11g Release 1 (11.1.0.7.0) for Microsoft Windows Windows Server 2008 media. In addition, for Windows Server 2008, you must have administrator privileges and you must run commands from an Administrative command prompt to run executables that reside in the Oracle Clusterware home.

5.1 Verifying Oracle Clusterware Requirements with CVU

Using the following command syntax, start Cluster Verification Utility (CVU) to check system requirements prior to installing Oracle Clusterware:

mountpoint\runcluvfy.bat stage -pre crsinst -n node_list

In the preceding syntax, replace mountpoint with the path for the installation media and the variable node_list with the names of the nodes in your cluster, separated by commas.

For example, with the installation files in a stage directory on the C: drive, enter the following command for a cluster with nodes node1, node2, and node3:

c:\stage\db\Disk1\runcluvfy.bat stage -pre crsinst -n node1,node2,node3

The Cluster Verification Utility Oracle Clusterware stage check verifies the following:

  • User Equivalence: User equivalence exists on all the specified nodes

  • Node Reachability: All the specified nodes are reachable from the local node

  • Node Connectivity: Connectivity exists between all the specified nodes through the public and private network interconnections

  • Administrative Privileges: The oracle user has proper administrative privileges to install Oracle Clusterware on the specified nodes

  • Shared Storage Accessibility: If specified, the Oracle Cluster Registry (OCR) device and voting disk are shared across all the specified nodes

  • System Requirements: All system requirements are met for installing Oracle Clusterware software, including software packages, memory, swap directory space, temp directory space, and required users and groups

5.1.1 Troubleshooting Clusterware Setup for Windows

If the CVU report indicates that your system fails to meet the requirements for Oracle Clusterware installation, then use the topics in this section to correct the problem or problems indicated in the report, and run the CVU command again.

User Equivalence Check Failed
Cause: Failure to establish user equivalency across all nodes. This can be due to not providing the Administrative user on each node with the same password.
Action: Either the same local administrative username and password must be used on every node in a cluster, or the same domain user with local administrative privileges must be used on all nodes. If you use a domain user, then the domain user must be in the same domain on every node.
Node Reachability Check
Cause: One or more nodes in the cluster cannot be reached using TCP/IP protocol, through either the public or private interconnects.
Action: Use the command ping address to check each node address. When you find an address that cannot be reached, check your list of public and private addresses to make sure that you have them correctly configured. Ensure that the public and private network interfaces have the same interface names on each node of your cluster.
Administrative Privileges Check Failed
Cause: The administrative privileges required for installation are missing or incorrect.
Action: From the node where you intend to run OUI, verify that you have administrative privileges on the other nodes. To do this, enter the following command for each node that is a part of the cluster where nodename is the name of the node:
net use \\nodename\C$

If you cannot log on, then you must correct the user information on that node. You must use a domain user name, or the same user name and password on each node in a cluster. If you use a domain user name, then log on under a domain with a username and password that has local administrative privileges on each node. When you have corrected the path configuration information on the node, run the CVU check again.

5.2 Preparing to Install Oracle Clusterware with OUI

Before you install Oracle Clusterware, use the following checklist to ensure that you have all the information you will need during installation, and you have completed all tasks that must be done before starting to install Oracle Clusterware. Mark the check box for each task as you complete it, and write down the information needed, so that you can provide it during installation.

  • Verify Cluster Privileges

    Before running Oracle Universal Installer, from the node where you intend to run the Installer, verify that you have administrative privileges on the other nodes. To do this, enter the following command for each node that is a part of the cluster:

    net use \\nodename\C$
    

    where nodename is the node name.

  • Shut Down Running Oracle Processes

    If you are installing Oracle Clusterware on a node that already has a single-instance Oracle Database 11g release 1 (11.1) installation, then stop the existing ASM instances. After Oracle Clusterware is installed, start up the ASM instances again. When you restart the single-instance Oracle database, the ASM instances use the Cluster Synchronization Services (CSSD) Daemon from Oracle Clusterware instead of the CSSD daemon for the single-instance Oracle database.

    You can upgrade some or all nodes of an existing Cluster Ready Services installation. For example, if you have a six-node cluster, then you can upgrade two nodes each in three upgrading sessions.Base the number of nodes that you upgrade in each session on the load the remaining nodes can handle. This is called a "rolling upgrade."

    If a Global Services Daemon (GSD) from Oracle9i Release 9.2 or earlier is running, then stop it before installing Oracle Database 11g release 1 (11.1) Oracle Clusterware by running the following command:

    gsdctl stop
    

    from the Oracle Database home that is running the GSD.

    Caution:

    If you have an existing Oracle9i release 2 (9.2) Oracle Cluster Manager (Oracle CM) installation, then do not shut down the Oracle CM service. Shutting down the Oracle CM service prevents the Oracle Clusterware 11g release 1 (11.1) software from detecting the Oracle9i release 2 node list, and causes failure of the Oracle Clusterware installation.

    Note:

    If you receive a warning to stop all Oracle services after starting OUI, then run the command
    localconfig delete
    

    from the Oracle_home that is running CSS.

  • Determine your cluster name, public node names, private node names, and virtual node names for each node in the cluster

    If you install the clusterware during installation, then you are asked to provide a public node name and a private node name for each node. When you enter the public node name, use the primary host name of each node. In other words, use the name displayed by the hostname command but without any portion of the domain name that may be returned by the command.

    In addition, ensure that the following are true:

    • Determine a cluster name with the following characteristics:

      • It must be globally unique throughout your host domain

      • It must be at least one character long and less than 15 characters long

      • It must consist of the same character set used for host names: hyphens (-) and single-byte alphanumeric characters (a to z, A to Z, and 0 to 9). If you use third-party vendor clusterware, then Oracle recommends that you use the vendor cluster name

    • Determine a private node name or private IP address for each node. The private IP address is an address that is only accessible by the other nodes in this cluster. Oracle uses private IP addresses for inter-node, or instance-to-instance Cache Fusion traffic. Oracle recommends that you provide a name in the format public_hostname-priv, for example myclstr2-priv.

    • Determine a virtual host name for each node. A virtual host name is a public node name that is used to reroute client requests sent to the node if the node is down. Oracle uses virtual IP addresses (VIPs) for client to database connections, so the VIP address must be publicly accessible. Oracle recommends that you provide a name in the format public_hostname-vip, for example myclstr2-vip.

      Note:

      The following is a list of additional information about node IP addresses:
      • The IP addresses that you use for all of the nodes in the current installation process must be from the same subnet.

      • OUI fills the default private and virtual host names in the format nodename-priv and nodename-vip. You must fill in the addresses during installation if your host names differ from the default ones.

      • Host names, private names, and virtual host names are not domain-qualified. If you provide a domain in the address field during installation, then the OUI removes the domain from the address.

      • Private IP addresses should not be accessible as public interfaces. Using public interfaces for Cache Fusion can cause performance problems.

  • Determine the complete path for the raw devices or shared file systems, and set up the voting disk and Oracle Cluster Registry partitions

    During installation, at the Cluster Configuration Storage page, you are asked to provide paths for two files that must be shared across all nodes of the cluster, either on a shared raw device, or a shared file system file:

    • The Cluster Synchronization Services (CSS) voting disk is a partition that Oracle Clusterware uses to verify cluster node membership and status. Provide at least 280 MB of disk space for each voting disk.The Oracle Cluster Registry (OCR) contains cluster and database configuration information for the Oracle RAC database and for Oracle Clusterware, including the node list, and other information about cluster configuration and profiles. Provide at least 280 MB disk space for each Oracle Cluster Registry.

    In addition, if you intend to use Oracle Cluster File System (OCFS) then you are prompted to indicate which of the available disks you want to format with OCFS, what format type you want to use, and to what drive letter the formatted OCFS disk is mounted.

    Ensure that you create at least the minimum required drives for installation.

    See Also:

    Chapter 3 for information about the minimum raw device sizes
  • Disconnect all non-persistent drives

    Before starting the Oracle Clusterware installation on Windows platform, please make sure that you disconnect all nonpersistent drives that are temporarily mounted on all the nodes. Alternatively, if you want to access the shared drive, then make the shared drive persistent using the following command:

    net use * \\servername\sharename /persistent: YES
    

5.3 Installing Oracle Clusterware with OUI

This section provides you with information about how to use Oracle Universal Installer (OUI) to install Oracle Clusterware. It contains the following sections:

5.3.1 Running OUI to Install Oracle Clusterware

Perform the following procedures to install Oracle Clusterware with OUI. You can run OUI from a VNC session, or Terminal Services in console mode.

  1. Log in to Windows with Administrative privileges and run the setup.exe command from the \Disk1 directory on the Oracle Database 11g release 1 (11.1) installation media.

    The setup.exe command opens the OUI Select a Product to Install page. Select Oracle Clusterware and click Next.

  2. After you click Next, the Specify Home Details page enables you to accept the displayed path name for the Oracle Clusterware products or select a different one. You may also accept default directory and path name for the location of your Oracle Clusterware home or browse for an alternate directory and destination. You must select a destination that exists on each cluster node that is part of this installation. Click Next to confirm your choices.

  3. The installer verifies that your environment meets all of the minimum requirements for installing and configuring the products that you have chosen to install. The results are displayed on the Product-Specific Prerequisite Checks page. Verify and confirm the items that are flagged with warnings and items that require manual checks. After you confirm your configuration, OUI displays the Specify Cluster Configuration page.

    Note:

    If the check identifies an existing, local CSS, then you must first shut down the Oracle Database and ASM instances from the Oracle home where CSS is running, and then run the following command from the same Oracle home before you continue with the installation:
    Oracle home\bin\localconfig delete
    
  4. The Specify Cluster Configuration page contains predefined node information.

    If OUI detects that your system has Oracle9i Release 2 clusterware, then the Specify Cluster Configuration page displays the existing node list. Otherwise, OUI displays the Specify Cluster Configuration page with local node only. You may need to modify the default private and virtual names for your environment.

    Provide a cluster name if you do not wish to use the name provided by OUI. Note that the selected cluster name must be globally unique throughout the enterprise. In addition, the allowable character set for cluster names is the same as that for hostnames, that is single-byte alphanumeric characters (a to z, A to Z, and 0 to 9), and hyphens (-).

    If you prefer, you may instead provide the cluster configuration information in a text file and provide that file name instead of completing the individual fields on the Specify Cluster Configuration page. See the following section, "Installing Oracle Clusterware Using a Cluster Configuration File", for details about cluster configuration files.

    Note:

    If you are upgrading your cluster or part of your cluster from Oracle9i release 2 Cluster Ready Services to Oracle Clusterware release 11g, then to ensure backward compatibility, OUI prevents you from changing the cluster name from the existing name by disabling the cluster name field.

    Click Next after you have entered the cluster configuration information. This saves your entries and opens the Specify Network Interface Usage page.

  5. In the Specify Network Interface Usage page OUI displays a list of cluster-wide interfaces. Use the drop-down menus on this page to classify each interface as Public, Private, or Do Not Use. You must classify at least one interface as Public and one as Private. Click Next when you have made your selections to open the Select Disk Formatting Options page.

  6. On the Cluster Configuration Storage page, identify the disks that you want to use for the Oracle Clusterware files and, optionally, Oracle Cluster File System (OCFS) storage. Highlight each of these disks one at a time and click Edit to open the Cluster Configuration Storage page on which you can define the details for selected disks.

    Note:

    The OUI page described in this step displays logical drives from which you must make your selections. If you have a previous version of Oracle Clusterware installed on the system, and the installer detects an existing voting disk and OCR on a OCFS or raw partition, then you do not need to create new partitions for the OCR and Voting disks when upgrading to Oracle Clusterware 11g.
  7. On the Cluster Configuration Storage page, designate whether you want to place a copy of the OCR, a copy of the voting disk, or a copy of both files (if CFS is selected) on the partition. If you plan to use CFS, then indicate whether you plan to store software, database files, or both software and database files on selected partition, and select an available drive letter to be used to mount the partition once formatted.

  8. After you click Next, OUI displays a Summary page that shows the cluster node information, along with the space requirements and availability. Verify the installation that OUI is about to perform and click Finish.

  9. When installation finishes successfully, click Exit.

At this point, you have completed the Oracle Clusterware installation.

To install Oracle Database 11g with Oracle RAC, refer to Oracle Real Application Clusters Installation Guide for Microsoft Windows. If you intend to use Oracle Clusterware without an Oracle RAC database, then refer to Oracle Database Installation Guide for Microsoft Windows.

5.3.2 Installing Oracle Clusterware Using a Cluster Configuration File

During the Oracle Clusterware installation, on the Specify Cluster Configuration page, you are given the option either of providing cluster configuration information manually, or of using a cluster configuration file. A cluster configuration file is a text file that you can create before starting OUI, which provides OUI with information about the cluster name and node names that it needs to configure the cluster.

Oracle suggests that you consider using a cluster configuration file if you intend to perform repeated installations on a test cluster, or if you intend to perform an installation on many nodes.

To create a cluster configuration file:

  1. On the installation media, navigate to the directory Disk1\response.

  2. Using a text editor, open the response file crs.rsp, and find the section CLUSTER_CONFIGURATION_FILE.

  3. Follow the directions in that section for creating a cluster configuration file.

Note:

For Windows Server 2008, you must have administrator privileges and you must run commands from an Administrative command prompt to run executables that reside in the Oracle Clusterware home.

5.3.3 Silent Installation of Oracle Clusterware

Complete the following procedure to perform a noninteractive (silent) installation:

  1. On the installation media, navigate to the directory Disk1\response.

  2. Using a text editor, open the response file crs.rsp. Follow the directions in each section, and supply values appropriate for your environment.

  3. Use the following command syntax to run OUI in silent mode:

    setup.exe -silent -reponseFile path_to_your_reponse_file
    

    For example:

    C:\ setup.exe -silent -responseFile \download\oracle\Disk1\response\mycrs.rsp
    

Note:

For Windows Server 2008, you must have administrator privileges and you must run commands from an Administrative command prompt to run executables that reside in the Oracle Clusterware home.

5.4 Formatting Drives to Use Oracle Cluster File System after Installation

If you install Oracle Database 11g with Oracle RAC, and later you want to install OCFS, then run the ocfsformat.exe command from the crs_home\cfs directory using the following syntax:

crs_home\cfs\OcfsFormat /m drive_letter /c clustersize [/v volume_label] [/f]

Where:

  • /m drive_letter is the mountpoint for the file system which you want to format with OCFS. On Windows, provide a drive letter corresponding to the logical drive.

  • clustersize is the size of the cluster in kilobytes

  • volume_label is an optional volume label

Note:

The clustersize is essentially the block size. Recommended values are 1024 (1 MB) if the OCFS partition is to be used for Oracle datafiles and 4 (4 KB) if the OCFS partition is to be used for the ORACLE_HOME.