9.5 Installing Oracle Grid Infrastructure for a New Cluster

Complete this procedure to install Oracle Grid Infrastructure (Oracle Clusterware and Oracle ASM) on your cluster.

If you have any questions during installation, then click the Help button on the installer page.

You should have your network information, storage information, and operating system users and groups available to you before you start installation.

  1. Log in to Windows as the installation user for Oracle Grid Infrastructure, which must be a member of the Administrators users group.
  2. Create the Grid home directory.

    For example:

    md C:\app\21.0.0\grid
    

    Ensure that the Grid home directory path you create is in compliance with the Oracle Optimal Flexible Architecture recommendations.

  3. Download the Oracle Grid Infrastructure image files and copy the files to the Grid home.

    For example:

    cd C:\app\21.0.0\grid
    unzip -q download_location\grid_home.zip

    Unzip the installation image files only in this Grid home directory that you created.

    Note:

    Download and copy the Oracle Grid Infrastructure image files to the local node only. During installation, the software is copied and installed on all other nodes in the cluster.

  4. Start the Oracle Grid Infrastructure Setup Wizard by running the following command:
    Grid_home\setup.exe
    You can run this command from a Virtual Network Computing (VNC) session, or Terminal Services in console mode.
  5. Select one of the following configuration options:
    • Configure Oracle Grid Infrastructure for a New Cluster

      Select this option to configure a new Oracle Flex Cluster deployment.

    • Configure Oracle Grid Infrastructure for a standalone server (Oracle Restart)

      Select this option to install Oracle Grid Infrastructure in an Oracle Restart configuration. Use this option for single servers supporting Oracle Database and other applications.

    • Upgrade Oracle Grid Infrastructure

      Select this option to upgrade Oracle Grid Infrastructure (Oracle Clusterware and Oracle ASM).

    • Set Up Software Only

      Select this option to configure Oracle Grid Infrastructure software and register the Oracle Grid Infrastructure home with the central inventory

  6. Choose the type of Oracle Flex Cluster from the following options:
    • Configure an Oracle Standalone Cluster: Select this option to install Oracle Grid Infrastructure software for Oracle Standalone Cluster.

    • Configure an Oracle Domain Services Cluster: Select this option to install Oracle Grid Infrastructure software for Oracle Domain Services Cluster.

      Note:

      Oracle Domain Services Cluster is not supported on Microsoft Windows.

      Configure as an Oracle Extended Cluster: Select this option to extend an Oracle RAC cluster across two or more separate sites, each equipped with its own storage.

  7. In the Grid Plug and Play Information window, select SCAN option for the local cluster:
    • Select Create Local SCAN to create a SCAN locally. Enter the values in the Cluster Name, SCAN Name, and SCAN Port fields that are unique throughout your entire enterprise network.
    • Select Configure GNS if you have configured your domain name server (DNS) to send to the GNS virtual IP address name resolution requests for the subdomain GNS servers.
    • Select Use Shared GNS if you have configured a shared GNS on one cluster to provide name resolution for all clusters. Specify the complete path to the GNS client data file in the GNS Client Data field.
  8. Respond to the installation screens that appear in response to your configuration selection.
    Installation screens vary depending on the installation option you select.

    For cluster member node public and VIP network addresses, provide the information required depending on the kind of cluster you are configuring:

    • If you plan to use automatic cluster configuration with DHCP addresses configured and resolved through GNS, then you only need to provide the GNS VIP names as configured on your DNS.

    The following is a list of additional information about node IP addresses:

    • For the local node only, the installer automatically fills in public and VIP fields. If your system uses vendor clusterware, then the installer may fill additional fields.

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

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

    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.

  9. Select storage option for Oracle Cluster Registry (OCR) and voting files:
    1. Select Use Oracle Flex ASM for storage to store OCR and voting files on an Oracle ASM disk group.
    2. Select Configure as ASM Client Cluster to store OCR and voting files on an Oracle ASM disk group configured on a storage server cluster. Specify the complete path to the ASM client data file in the ASM Client Data field.
  10. In the Create GIMR Option window, select an option to create a Grid Infrastructure Management Repository for your Oracle Standalone Cluster installation:
    • Select Yes to create a GIMR by installing Oracle RAC software and creating GIMR container database after completing Oracle Grid Infrastructure installation.
    • Select Use an Existing GIMR database to use a remote GIMR and specify a GIMR credentials file.
    • Select No if you do not want to create a GIMR.
    If you choose Yes on this window, then the Grid Infrastructure Management Repository Option window appears. Otherwise, the Create ASM Disk Group or ASM Client Storage Option window appears, based on your storage option. If you choose No on this window and you create a GIMR later, then create a separate Oracle ASM disk group for GIMR using Oracle ASMCA.
  11. Choose whether you want to store the Grid Infrastructure Management Repository in a separate Oracle ASM disk group.
  12. Provide the name and specifications for the Oracle ASM disk group.
    • In the Disk Group Name field, enter a name for the disk group, for example DATA.
    • Choose the Redundancy level for this disk group. Normal is the recommended option.
    • In the Add Disks section, choose the disks to add to this disk group.
    • If you want to use Oracle ASM Filter Driver (Oracle ASMFD) to manage your Oracle ASM disk devices, then select the option Configure Oracle ASM Filter Driver.
  13. If you selected to use ASM client cluster in Step 9, then ASM Client Storage Option window appears. Select an Oracle ASM disk group from the storage server cluster to store the OCR and voting files.
  14. Respond to the installation screens that appear in response to your configuration selection.
  15. Provide information and run scripts as prompted by the installer.
    After the installation interview, you can click Details to see the log file.
  16. After you have specified all the information needed for installation, the installer installs the software on each node. The installer then runs Oracle Net Configuration Assistant (NETCA), Oracle Private Interconnect Configuration Assistant, and Cluster Verification Utility (CVU). These programs run without user intervention.
  17. During the installation, Oracle Automatic Storage Management Configuration Assistant (asmca) configures Oracle ASM for storage.

When you have verified that your Oracle Grid Infrastructure installation has completed successfully, you can either use Oracle Clusterware and Oracle ASM to maintain high availability for other applications, or you can install Oracle Database and Oracle RAC software.

You can manage Oracle Grid Infrastructure and Oracle Automatic Storage Management (Oracle ASM) using Oracle Enterprise Manager Cloud Control. To register the Oracle Grid Infrastructure cluster with Oracle Enterprise Manager, ensure that Oracle Management Agent is installed and running on all nodes of the cluster.