| Oracle® Grid Infrastructure Installation Guide 11g Release 2 (11.2) for IBM AIX on POWER Systems (64-Bit) Part Number E10814-01 |
|
|
View PDF |
| Oracle® Grid Infrastructure Installation Guide 11g Release 2 (11.2) for IBM AIX on POWER Systems (64-Bit) Part Number E10814-01 |
|
|
View PDF |
This chapter describes the difference between a Typical and Advanced installation for Oracle grid infrastructure for a cluster, and describes the steps required to complete a Typical installation.
This chapter contains the following sections:
You are given two installation options for Oracle grid infrastructure installations:
Typical Installation: The Typical installation option is a simplified installation with a minimal number of manual configuration choices. Oracle recommends that you select this installation type for most cluster implementations.
Advanced Installation: The Advanced Installation option is an advanced procedure that requires a higher degree of system knowledge. It enables you to select particular configuration choices, including additional storage and network choices, use of operating system group authentication for role-based administrative privileges, or more granularity in specifying Automatic Storage Management roles.
With Oracle Clusterware 11g release 2 (11.2), during installation Oracle Universal Installer (OUI) generates Fixup scripts (runfixup.sh) that you can run to complete required preinstallation steps.
The fixup script is generated during installation. You are prompted to run the script as root in a separate terminal session. When you run the script, it completes the following configuration tasks:
If necessary sets kernel parameters required for installation and runtime to at least the minimum value.
Complete the following manual configuration tasks
See Also:
Chapter 2, "Advanced Installation Oracle Grid Infrastructure for a Cluster Preinstallation Tasks" and Chapter 3, "Configuring Storage for Grid Infrastructure for a Cluster and Oracle Real Application Clusters (Oracle RAC)" if you need any information about how to complete these tasksEnter the following commands to check available memory:
# /usr/sbin/lsattr -E -l sys0 -a realmem # /usr/sbin/lsps -a
The minimum required RAM is 1.5 GB for grid infrastructure for a cluster, or 2.5 GB for grid infrastructure for a cluster and Oracle RAC. The minimum required swap space is 1.5 GB. Oracle recommends that you set swap space to 1.5 times the amount of RAM for systems with 2 GB of RAM or less. For systems with 2 GB to 16 GB RAM, use swap space equal to RAM. For systems with more than 16 GB RAM, use 16 GB of RAM for swap space.
Verify the space available for Oracle Clusterware files using one of the following commands, depending on where you intend to place Oracle Clusterware files:
GPFS:
/usr/bin/df -k
To check raw device volumes in preparation for installing Oracle ASM disk groups, use the following checks:
Raw Logical Volumes in Concurrent VG (HACMP): In the following example, the variable lv_name is the name of the raw logical volume whose space you want to verify:
lslv lv_name
Raw hard disks: In the following example, the variable rhdisk# is the raw hard disk number that you want to verify, and the variable size_mb is the size in megabytes of the partition that you want to verify:
lsattr -El rhdisk# -a size_mb
If you use normal redundancy for Oracle Clusterware files, which is 3 Oracle Cluster Registries (OCR) and 3 voting disks, ideally, in different file systems on independent disks, then you should have at least 1 GB of disk space available on separate physical disks reserved for Oracle Clusterware files. Each file system for the Oracle Clusterware files should be at least 280 MB in size.
Note:
You cannot install OCR or voting disk files on raw partitions. You can install only on Oracle ASM, or on supported network-attached storage or cluster file systems. The only use for raw devices is as ASM disks.To ensure high availability of Oracle Clusterware files on Oracle ASM, you need to have at least 2 GB of disk space for Oracle Clusterware files in three separate failure groups, with at least three physical disks. Each disk must have at least 1 GB of capacity to ensure that there is sufficient space to create Oracle Clusterware files.
Ensure you have at least 12 GB of space for the grid infrastructure for a cluster home (Grid home) This includes Oracle Clusterware and Automatic Storage Management (Oracle ASM) files and log files.
/usr/bin/df -k /tmp
Ensure that you have at least 1 GB of space in /tmp. If this space is not available, then increase the size, or delete unnecessary files in /tmp.
For more information, review the following section in Chapter 2:
Ensure that you have the following available:
During Typical installation, you are prompted to confirm the default Single Client Access Name (SCAN), which is used to connect to databases within the cluster irrespective of which nodes they are running on. By default, the name used as the SCAN is also the name of the cluster. The default value for the SCAN is based on the local node name. If you change the SCAN from the default, then the name that you use must be globally unique throughout your enterprise.
In a Typical installation, the SCAN is also the name of the cluster. The SCAN and cluster name must be at least one character long and no more than 15 characters in length, must be alphanumeric, and may contain hyphens (-).
For example:
NE-Sa89
If you require a SCAN that is longer than 15 characters, then be aware that the cluster name defaults to the first 15 characters of the SCAN.
Refer to the following section for the SCAN address requirements.
Before starting the installation, you must have at least two interfaces configured on each node: One for the private IP address and one for the public IP address.
Note:
Oracle recommends that you use a static hostname for all server node public hostnames.The public and virtual IP addresses must be static addresses, configured before installation, and the virtual IP addresses for each node must not currently be in use. Oracle Clusterware manages private IP addresses in the private subnet on interfaces you identify as private during the installation interview.
Configure the following addresses:
A public IP address for each node
A virtual IP address for each node
A single client access name (SCAN) configured on the domain name server (DNS) for Round Robin resolution to three addresses (recommended) or at least one address.
The single client access name (SCAN) is a cluster alias used to provide service access for clients to the cluster. Because the SCAN is associated with the cluster as a whole, rather than to a particular node, the SCAN makes it possible to add or remove nodes from the cluster without needing to reconfigure clients. It also adds location independence for the databases, so that client configuration does not have to depend on which nodes are running a particular database. Clients can continue to access the cluster in the same way as with previous releases, but Oracle recommends that clients accessing the cluster use the SCAN.
Note:
Oracle strongly recommends that you do not configure SCAN VIP addresses in the hosts file. Use DNS resolution for SCAN VIPs.During installation, you are asked to identify the planned use for each network interface that OUI detects on your cluster node. You must identify each interface as a public or private interface, and you must use the same private interfaces for both Oracle Clusterware and Oracle RAC. For interfaces that you plan to have used for other purposes--for example, an interface dedicated to a network file system--you must identify those instances as "do not use" interfaces, so that Oracle Clusterware ignores them.
You can bond separate interfaces to a common interface to provide redundancy, in case of a NIC failure, but Oracle recommends that you do not create separate interfaces for Oracle Clusterware and Oracle RAC. If you use more than one NIC for the private interconnect, then Oracle recommends that you use NIC bonding. Note that multiple private interfaces provide load balancing but not failover, unless bonded.
Refer to the tables listed in Section 2.8, "Checking the Software Requirements" for the list of required packages for your operating system.
Enter the following commands to create default groups and users:
One system privileges group for all operating system-authenticated administration privileges, including Oracle RAC (if installed):
# mkgroup -'A' id='1000' adms='root' oinstall # mkgroup -'A' id='1200' dba # mkuser id='1100' pgrp='oinstall' groups='dba' adms='root' home='/home/grid' grid # mkuser id='1101' pgrp='oinstall' groups='dba' adms='root' home='/home/oracle' oracle # mkdir -p /u01/grid # chown -R grid:oinstall /u01 # mkdir /u01/app/oracle # chown oracle:oinstall /u01/app/oracle # chmod -R 775 /u01/
Ensure that the grid infrastructure installation owner account has the capabilities CAP_NUMA_ATTACH, CAP_BYPASS_RAC_VMM, and CAP_PROPAGATE.
To check existing capabilities, enter the following command as root; in this example, the Grid installation user account is grid:
# /usr/bin/lsuser -a capabilities grid
To add capabilities, enter a command similar to the following:
# /usr/bin/chuser capabilities=CAP_NUMA_ATTACH,CAP_BYPASS_RAC_VMM,CAP_PROPAGATE grid
Set the password on the grid installation owner account:
passwd grid
Repeat this process for each cluster member node.
Set shell limits for the grid infrastructure installation owner and for root to unlimited. Verify that unlimited is set for both accounts either by using the smit utility or by editing the /etc/security/limits file. The root user requires these settings because the crs daemon (crsd) runs as root. Add the following lines to the limits file:
default:
fsize = -1
core = 2097151
cpu = -1
data = -1
rss = -1
stack = -1
nofiles = -1
You must have space available either on a supported file system, or on Oracle Automatic Storage Management for Oracle Clusterware files (voting disks and Oracle Cluster Registries), and for Oracle Database files, if you install standalone or Oracle Real Application Clusters Databases. Creating Oracle Clusterware files on block or raw devices is no longer supported for new installations.
Review the relevant sections in Chapter 3 for the installation option you want to configure.
Start OUI from the root level of the installation media. For example:
./runInstaller
Select Install and Configure Grid Infrastructure for a Cluster, then select Typical Installation. In the installation screens that follow, enter the configuration information as prompted.
If you receive an installation verification error that cannot be fixed using a fixup script, then review Chapter 2, "Advanced Installation Oracle Grid Infrastructure for a Cluster Preinstallation Tasks" to find the section for configuring cluster nodes. After completing the fix, continue with the installation until it is complete.
|
 Copyright © 2007, 2009, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|