| Oracle® Grid Infrastructure Installation Guide 11g Release 2 (11.2) for Microsoft Windows Part Number E10817-01 |
|
|
View PDF |
| Oracle® Grid Infrastructure Installation Guide 11g Release 2 (11.2) for Microsoft Windows Part Number E10817-01 |
|
|
View PDF |
This chapter describes the differences 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 level of system knowledge. It enables you to select particular configuration choices, including additional storage and network choices, integration with Intelligent Platform Management Interface (IPMI), or more granularity in specifying Oracle Automatic Storage Management roles.
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 RAC" for information about how to complete these tasksThis section provides a summary of the following pre-installation tasks:
For more information about these tasks, review "Checking the 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, or Settings. In the Performance Options window, the virtual memory, or page file, select the Advanced tab and the settings are displayed at the bottom of the window.
The minimum required RAM is 1.5 GB for Oracle grid infrastructure, and the minimum required virtual memory space is 2 GB. Oracle recommends that you set the paging file size to twice the amount of RAM.
If you also plan to install Oracle RAC, then 2.5 GB of memory is the minimum required RAM.
The minimum processor speed is 1GHz for Windows Server 2003, Windows Server 2003 R2, and Windows Server 2008. The minimum processor speed is 1.4GHz for Windows Server 2008 R2.
From the Start menu, select Run... In the Run window, type in Diskmgmt.msc to open the Disk Management GUI interface.
The Disk Management window displays the available space on file systems. If you use standard redundancy for Oracle Clusterware files, which is 3 Oracle Cluster Registry (OCR) files and 3 voting disk files, then you should have at least 2 GB of disk space available on three separate physical disks reserved for Oracle Clusterware files.
Ensure you have at least 3 GB of space for the grid infrastructure for a cluster home (Grid home). This includes Oracle Clusterware and Oracle Automatic Storage Management (Oracle ASM) files and log files.
Ensure that you have at least 1 GB 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 TEMP and TMP both point to the location of the TEMP directory, for example:
TEMP=C:\WINDOWS\TEMP TMP=C:\WINDOWS\TEMP
Ensure that you have the following available:
During Typical installation, you are prompted to confirm the default Single Client Access Name (SCAN) for the cluster, which is used to connect to databases within the cluster irrespective of which nodes the database instances are running on. 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 can contain hyphens (-). For example:
sales-dev
If you require a SCAN that is longer than 15 characters, then select the Advanced installation option. See "IP Address Requirements" for information about the SCAN address requirements.
Before starting the installation, you must have at least two network interface cards configured on each node: One for the private IP addresses and one for the public IP addresses.
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 network adapters you identify as private during the installation interview.
Configures and updates the GPnP profile with 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 host name used to provide 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 instance. Client 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:
If you manually configure addresses, the Oracle strongly recommends that you use DNS resolution for SCAN VIPs. If you use the hosts file to resolve SCANs, then you must provide a hosts file entry for each SCAN address.See Also:
"Understanding Network Addresses" for more information about network addresses.During installation, you are asked to identify the planned use for each network adapter that Oracle Universal Installer (OUI) detects on your cluster node. You must identify each adapter as a public or private adapter, and you must use the same private adapters for both Oracle Clusterware and Oracle RAC. For adapters that you plan to use for other purposes–for example, an adapter dedicated to a network file system–you must identify those adapters as "do not use" so that Oracle Clusterware ignores them.
Media Sense allows Windows to uncouple an IP address from a network interface card when the link to the local switch is lost. To disable Windows Media Sensing for TCP/IP on Windows Server 2003 with SP1 or higher, 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 (Regedit.exe) to view the following key in the registry:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters
Add a new DWORD value to the Parameters subkey:
Value Name: DisableDHCPMediaSense Value: 0
Exit the Registry Editor and then restart the computer.
Check the network adapter binding order on each node. Ensure that your public network adapter is first in the bind order, and the private network adapter is second. Follow these steps to configure the network adapter bind order:
Right-click My Network Places and choose Properties.
In the Advanced menu, click Advanced Settings.
If the public adapter 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 adapter (such as public) must be consistent across all nodes. You can use nondefault names for the network adapter, for example, PublicLAN, as long as the same names are used for the same class of network adapters on each node in the network.
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$
Refer to the tables listed in "Identifying Software Requirements" for details.
You must configure sufficient space in the Windows paging file. Paging files are used to store pages of memory used by the process that are not contained in other files. Paging files are shared by all processes, and the lack of space in paging files can prevent other processes from allocating memory.
If possible, split the paging file into multiple files on multiple physical devices. This encourages parallel access to virtual memory, and improves the software performance. See "Memory Requirements" for information on configure the Windows paging file.
To install the Oracle software, you must use an account with administrative privileges. For more information, refer to 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 environment variables should point to the same local directory on 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:\temp and WIN_DRIVE:\tmp, for example, C:\temp or C:\tmp for all nodes, if Windows is installed on the C drive.
The directory that Oracle software is installed in is referred to as its home directory. When installing Oracle Grid Infrastructure, you must determine the location of the Oracle Grid Infrastructure home. Oracle Automatic Storage Management is also installed in this home directory. When you install Oracle RAC, you must choose a different directory to install the software. The location of the Oracle RAC installation is referred to as the Oracle home.
The Oracle Inventory directory is the central inventory location for all Oracle software installed on a server. By default, the location of the Oracle Inventory directory is C:\Program Files\Oracle\Inventory.
For installations with Oracle Grid Infrastructure only, Oracle recommends that you let Oracle Universal Installer (OUI) create the Oracle Grid Infrastructure home and Oracle Inventory directories for you.
You must have space available 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 raw devices is no longer supported for new installations.
The following sections outline the procedure for creating OCR and voting disk partitions for Oracle Cluster File System for Windows (OCFS for Windows), and preparing disk partitions for use with Oracle ASM.
For additional information, review the following sections:
Note:
When using Oracle Automatic Storage Management (Oracle ASM) for either the Oracle Clusterware files or Oracle Database files, Oracle creates one Oracle ASM instance on each node in the cluster, regardless of the number of databases.The following steps outline the procedure for creating disk partitions for use with either OCFS for Windows or Oracle ASM:
Use Microsoft Computer Management utility or the command line tool diskpart to create an extended partition. Use a basic disk: dynamic disks are not supported.
Create at least one logical partition 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 for Windows. Oracle Clusterware creates individual files for the OCR and voting disk.
If your file system does not use RAID, then create an additional extended partition and logical partition for each partition that will be used by Oracle Clusterware files, to provide redundancy.
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:
For Windows Server 2003 and Windows 2003 R2 systems:
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.
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.
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.
For Windows Server 2008 and Windows Server 2008 R2 systems:
See "Configuring Storage for Oracle Database Files on OCFS for Windows" for instructions on creating disk partitions using the DISKPART utility.
Repeat Step 1 to create all the required partitions.
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
If you plan to use Oracle ASM to store the Oracle Clusterware files, then you must perform one additional step. After you have created the disk partitions, the disks must be stamped with a header before they can be used by Oracle ASM. You can configure the disk partitions manually by using either asmtoolg (GUI version) or using asmtool (command line version).
For more information about 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 "Installing Grid Infrastructure with OUI".
Start OUI from the root level of the installation media. For example:
cd D: setup.exe
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.
After you have installed Oracle Grid Infrastructure, apply any available patch sets or critical patches for Oracle Clusterware and Oracle ASM 11g release 2 (11.2).
|
 Copyright © 2007, 2010, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|