D59999GC30_les04

8/11/2019 D59999GC30_les04

1/24

Copyright 2012, Oracle and/or i ts affiliates. All rights reserved.

Grid Infrastructure Installation

8/11/2019 D59999GC30_les04

2/24Oracle Grid Infrastructure 11g: Manage Clusterware and ASM 4 - 2


Objectives

After completing this lesson, you should be able to:

Install Grid Infrastructure Verify the installation

ConfigureAutomatic Storage Management (ASM) disk

groups

Configure ASM volumes

Make the ASM cluster file system

Mount ASM Cluster File System (ACFS) volumes

8/11/2019 D59999GC30_les04

3/24

8/11/2019 D59999GC30_les04

4/24

On the Select Installation Option page, click the Install and Configure Grid Infrastructure Fora Cluster button and click Next

On the Installation Type page, you may choose a Typical Installation employing a basic fixed

IP configuration. You may also choose an Advanced Installation incorporating Grid Plug and

Play (GPnP) and offering greater flexibility in configuring:

Shared storage for OCR and voting files

Network options such as Grid Naming Service (GNS)

Failure isolation support employing Intelligent Platform Management Interface (IPMI)

Because the Typical Installation option assumes a basic configuration, the interview process

is shortened.

Oracle Grid Infrastructure 11g: Manage Clusterware and ASM 4 - 4


Choosing an Installation Type

8/11/2019 D59999GC30_les04

5/24

Grid Plug and Play Support: Advanced InstallationAfter you have chosen product languages from the Select Product Languages page, the Grid

Plug and Play Information page is displayed. You must supply a cluster name. This nameshould be unique within your subnet. If Grid Control is used, the cluster name should be

unique within the Grid Control management realm.

The single-client access name (SCAN) is the address used by clients connecting to thecluster. The SCAN is a domain name registered to three IP addresses, either in the domain

name server (DNS) or the Grid Naming Service (GNS). The SCAN addresses need to be onthe same subnet as the VIP addresses for the nodes in the cluster. The SCAN domain name

must be unique within your corporate network. The SCAN port should default to 1521 unless

you have a conflict at that port.

If you specify a GNS subdomain, the SCAN defaults to clustername-scan.GNSdomain. Forexample, if you start the Oracle Grid Infrastructure installation from the racnode01 server,the cluster name is cluster01 and the GNS domain is cluster01.example.com, then

the SCAN is cluster01-scan.cluster01.example.com.

If you do not use GNS, the SCAN should be defined in the DNS to resolve to the addressesassigned to that name. Assign three addresses to the SCAN. Finally, you must provide the

address of your GNS. This address must be resolvable through your DNS.



Grid Plug and Play Support

8/11/2019 D59999GC30_les04

6/24

Cluster Node Information: Advanced InstallationOn the Cluster Node Information page, the public host names and virtual host names are

defined. In the past, the host and VIP names and addresses were defined in the DNS orlocally in a hosts file. If you want to configure your cluster in this manner, make sure that the

Configure GNS check box is deselected on the previous screen. Click the Add button and

enter the Public Node Name and Virtual Host Name for each node in the cluster.

If GNS has been selected on the previous screen and DHCP is configured in the subdomain

in which the cluster resides, then configuration is simplified. Click the Add button, and thenadd the host name as shown in the graphic in the slide. There is no need to provide a Virtual

IP name for each node because Virtual IP names are automatically configured by Clusterware

using DHCP.

Secure Shell (SSH) can be configured for the specified nodes by clicking the SSH

Connectivity button. You will be required to provide the software owners password common to

all nodes. When SSH connectivity has been established, click Next to continue.



Cluster Node Information

8/11/2019 D59999GC30_les04

7/24

Specify Network Interface Usage: Advanced InstallationOn the Specify Network Interface Usage page, you can select the network interfaces on your

cluster nodes to use for internode communication. You must choose one interface for thepublic network and one for the private network. Ensure that the network interfaces that you

choose for the interconnect have enough bandwidth to support the cluster and RAC-related

network traffic. A gigabit Ethernet interface is highly recommended for the private

interconnect. To configure the interface for private use, click the interface type and choose the

proper usage for each network interface. In the example shown in the slide, there are twointerfaces: eth0 and eth1. The eth0 interface is the hosts primary network interface and

should be marked Public. The eth1 interface is configured for the private interconnect and

should be marked Private. If you have other adapters dedicated to a storage network, theyshould be marked Do Not Use. When you finish, click the Next button to continue.



Specify Network Interface Usage

8/11/2019 D59999GC30_les04

8/24

Storage Option Information: Advanced InstallationOn the Storage Option Information page, you can select your preferred method for storingClusterware files. The first option is Automatic Storage Management (ASM). The ability to use

ASM disk groups for Clusterware OCR and voting disks is a new feature in Oracle Database11gRelease 2 Grid Infrastructure. If you choose this option and ASM is not yet configured,OUI launches the ASM configuration assistant to configure ASM and a disk group to supportthe chosen configuration as il lustrated in the slide. When using ASM, the redundancy for theOCR and voting files is tied to the redundancy that you define for the disk group and thenumber of disks you put in the disk group. The voting disk is specifically allocated to threedisks in the disk group under normal redundancy and five disks under high redundancy. Bydefault, each disk in the disk group is put in its own failure group and the voting disks are put

into different failure groups. The OCR is stored similar to the way database files are stored.The other storage option available is shared file system storage. Suitable file systems includesupported cluster file systems such as OCFS2 or Network File System (NFS). If you selectShared File System on the Storage Option Information page, you will be prompted to providea cluster file system or NFS directory to be used for the OCR and voting disk files as shown inthe slide.The next page displayed is the Specify ASM Password page. The new ASM instance requiresits own SYS user with SYSASM privileges. Specify a secure password here and click Next tocontinue.



Storage Option Information

8/11/2019 D59999GC30_les04

9/24

If you choose not to implement GNS, you can choose Typical Installation from the SelectInstallation Type page. On the Specify Cluster Configuration page, you must enter the SCAN.The SCAN should be unique in your network. In a non-GNS environment, the SCAN shouldbe defined in the DNS or locally in the /etc/hosts file. If the SCAN is defined locally, you

are limited to one SCAN. If it is defined in DNS, you can have as many SCANs as you deem

necessary, although three SCANs are recommended.

Click the Add button to add cluster node information for the remaining nodes that will beincluded in this installation. You must provide the host name and VIP name for the additionalnodes. Both these names must be resolvable, either locally from the /etc/hosts file or from

your DNS.



Specify Cluster Configuration: Typical Installation

8/11/2019 D59999GC30_les04

10/24

Secure Shell (SSH) can be configured for the software owner on the specified nodes byclicking the SSH Connectivity button. You will be required to provide the software ownerspassword and it should be identical for all nodes. Click the Setup button to initiate the

configuration. If SSH has already been configured for the software owner, you could click the

Test button to check the existing configuration.

Click the Specify Network Interfaces button and select the network interfaces on your cluster

nodes to use for internode communication. You must choose one interface for the publicnetwork and one for the private network. Ensure that the network interfaces that you choose

for the interconnect have enough bandwidth to support the cluster and RAC-related network

traffic. For each adapter shown, click the interface type and choose the proper usage for each

one. In the example shown in the slide, there are two interfaces: eth0 and eth1. The eth0interface is the hosts primary network interface and should be marked Public. The eth1interface is configured for the private interconnect and should be marked Private. When

finished, click OK, and then the Next button to continue.



Specify Cluster Configuration: Typical Installation

8/11/2019 D59999GC30_les04

11/24

On the Specify Install Locations page, you must enter a base location for installing Oraclesoftware. A separate Oracle base should be created for each operating system user owningan Oracle software installation. In the example in the slide, that location is /u01/app/grid.

In the Software Location field, enter a directory in which to install Oracle Grid Infrastructure. Inthe example, the grid operating system user will own this installation, so the softwarelocation should be /u01/app/11.2.0/grid.

Next, you must indicate where the cluster registry and voting disks will be stored. In theexample in the slide, Oracle Automatic Storage Management (ASM) is chosen. If you choose

ASM, you must also assign the SYSASM password and the OSASM group. If you choose a

cluster file system instead of ASM for the Cluster Registry Storage type, you must provide a

valid path to that shared storage. When you have finished, click Next to continue.If you selected ASM for the Cluster Registry Storage type, you will be prompted to configure

an ASM disk group. Click the Change Discovery Path button and provide a path to all disks

intended for ASM storage if necessary. Choose a name and desired Redundancy for the disk

group. Select the disks to be used for the disk group and click Next to continue.



Install Locations: Typical Installation

8/11/2019 D59999GC30_les04

12/24

Failure Isolation Support with IPMI: Advanced InstallationIntelligent Platform Management Interface (IPMI) provides a set of common interfaces tocomputer hardware and firmware that administrators can use to monitor system health and

manage the system. With Oracle Database 11gRelease 2, Oracle Clusterware can integrate

IPMI to provide failure isolation support and to ensure cluster integrity.

You must have the following hardware and software configured to enable cluster nodes to bemanaged with IPMI:

Each cluster member node requires a Baseboard Management Controller (BMC)running firmware compatible with IPMI version 1.5, which supports IPMI over local areanetworks (LANs) and is configured for remote control.

Each cluster member node requires an IPMI driver installed on each node. The cluster requires a management network for IPMI. This can be a shared network, but

Oracle recommends that you configure a dedicated network.

Each cluster nodes Ethernet port used by BMC must be connected to the IPMImanagement network.



Failure Isolation Support with IPMI

8/11/2019 D59999GC30_les04

13/24

If you intend to use IPMI, you must provide an administration account username andpassword to provide when prompted during installation.

Note: For Oracle Clusterware to communicate with BMC, the IPMI driver must be installedpermanently on each node, so that it is available on system restarts.

The IPMI driver is available on the Asianux Linux, Oracle Enterprise Linux, Red HatEnterprise Linux, and SUSE Enterprise Linux distributions supported with this release.


8/11/2019 D59999GC30_les04

14/24

Privileged Operating System Groups: Advanced InstallationOn the Privileged Operating System Groups page, you must specify the groups that the Grid

Infrastructure owner should belong to for proper operating system authentication to ASM. Theexample in the slide specifies asmdba for the ASM Database Administrator (OSDBA) group,asmoper for the ASM Instance Administration Operator (OSOPER) group, and asmadmin for

the ASM Instance Administrator (OSASM) group. Click Next to continue.



Privileged Operating System Groups

8/11/2019 D59999GC30_les04

15/24

Next, OUI displays the Specify Installation Location page. Enter a base location for installingOracle software. A separate Oracle base should be created for each operating system userowning an Oracle software installation. In the example in the slide, that location is/u01/app/grid.

In the Software Location field, enter a directory in which to install Oracle Grid Infrastructure. Inthe example, the grid operating system user will own this installation, so the softwarelocation should be /u01/app/11.2.0/grid. When you have entered proper Oracle Base

and Software Location values, click Next to continue.

On the Create Inventory page, enter a location under your Oracle Base to store the Oracle

Inventory. Click Next to continue.

Note: The Create Inventory page is common to both Advanced and Typical installation typesas are the remaining installation steps.



Installation and Inventory Locations

8/11/2019 D59999GC30_les04

16/24

With the introduction of Oracle Database 11gRelease 2, the OUI provides additionalguidance to ensure recommended deployment and to prevent configuration issues. Inaddition, configuration assistants validate configurations and provide scripts to fix issues that

you can use or choose to reject. Clicking the Fix & Check Again button opens a windowinstructing you to run a fixup script that must be run as root on all nodes before continuing.

The installer can determine whether the deficiency can be corrected, presenting the user

performing the installation with the option of allowing the OUI to correct the situation. Byclicking the Fix & Check Again button, a script is generated on the nodes where the deficientcondition exists. After executing the scripts as root on the nodes, the kernel parameter is

adjusted, allowing the installation to continue uninterrupted. When the prerequisite checks

have completed successfully, click Next to continue. It is possible that an installationdeficiency cannot be corrected with a generated fixup script. The installer will indicate thiswith a No in the Fixable column for that item.



Prerequisite Checks

8/11/2019 D59999GC30_les04

17/24

8/11/2019 D59999GC30_les04

18/24

After the Grid Infrastructure has been copied to the remote nodes, you will be prompted to runroot scripts on all installed nodes. If this is the first Oracle software initiated by the operatingsystem user, you will run the orainstRoot.sh scripts on all nodes as prompted by theinstaller. Next, you must execute the root.sh script on all nodes. When the root.sh script

finishes executing on the last node, click Finish to exit the installer.



Finishing the Installation

8/11/2019 D59999GC30_les04

19/24

8/11/2019 D59999GC30_les04

20/24

8/11/2019 D59999GC30_les04

21/24

3. Relock the Grid home and restart the cluster using the following command:

# perl rootcrs.pl -patch

4. Repeat steps 1 through 3 on each cluster member node.


8/11/2019 D59999GC30_les04

22/24

8/11/2019 D59999GC30_les04

23/24Oracle Grid Infrastructure 11g: Manage Clusterware and ASM 4 - 23


Summary

In this lesson, you should have learned how to:

Perform preinstallation tasks for Grid Infrastructure Install Grid Infrastructure

Verify the installation

Configure ASM disk groups

Configure ASM volumes

Make the ASM cluster file system

Mount ACFS volumes

8/11/2019 D59999GC30_les04

24/24


Practice 4: Overview

This practice covers the following topics:

Performing Grid Infrastructure preinstallation tasks Installing Oracle Grid Infrastructure

Documents

D59999GC30_les04