| 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 procedures for installing Oracle Grid Infrastructure for a cluster. Oracle Grid Infrastructure consists of Oracle Clusterware and Oracle Automatic Storage Management (Oracle ASM). If you plan afterward to install Oracle Database with Oracle Real Application Clusters (Oracle RAC), then this is phase one of a two-phase installation.
This chapter contains the following topics:
Note:
The second phase of an Oracle RAC installation, installing Oracle RAC, is described in Oracle Real Application Clusters Installation Guide.Before you install Oracle Grid Infrastructure with Oracle Universal Installer (OUI), use the following checklist to ensure that you have all the information you will need during installation, and to ensure that you have completed all tasks that must be done before starting your installation. Mark the box for each task as you complete it, and record 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 are logged in using a member of the Administrators group, and that this user is an Administrator user on the other nodes in the cluster. 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. Repeat for each node in the cluster.
Shut Down Running Oracle Processes
You may need to shut down running Oracle processes:
Installing on a node with a standalone database not using Oracle ASM: You do not need to shut down the database while you install Oracle Grid Infrastructure software.
Installing on an Oracle RAC database node: This installation requires an upgrade of Oracle Clusterware, because Oracle Clusterware is required to run Oracle RAC. As part of the upgrade, you must shut down the database one node at a time as the rolling upgrade proceeds from node to node.
If a Global Services Daemon (GSD) from Oracle9i Release 9.2 or earlier is running, then stop it before installing Oracle Grid Infrastructure by running the following command, where Oracle_home is the Oracle Database home that is running the GSD:
Oracle_home\bin\gsdctl stop
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 Grid Infrastructure 11g release 2 (11.2) software from detecting the Oracle9i release 2 node list, and causes failure of the Oracle Grid Infrastructure installation.Prepare for Oracle Automatic Storage Management and Oracle Clusterware Upgrade If You Have Existing Installations
During installation, you can upgrade existing Oracle Clusterware and clustered Oracle ASM installations to Oracle Grid Infrastructure 11g release 2.
When all member nodes of the cluster are running Oracle Grid Infrastructure 11g release 2 (11.2), then the new clusterware becomes the active version.
If you intend to install Oracle RAC, then you must first complete the upgrade to Oracle Grid Infrastructure 11g release 2 (11.2) on all cluster nodes before you install the Oracle Database 11g release 2 (11.2) version of Oracle RAC.
Note:
All Oracle Grid Infrastructure upgrades (upgrades of existing Oracle Clusterware and clustered Oracle ASM installations) are out-of-place upgrades.Obtain LOCAL_SYSTEM administrator access
Oracle Grid Infrastructure must be installed using an Administrator user, one with LOCAL_SYSTEM privileges, or a member of the local Administrators group. If you do not have Administrator access to each node in the cluster, then ask your system administrator to create and configure the user account on each node.
Decide if you want to install other languages
During an Advanced installation session, you are asked if you want translation of user interface text into languages other than the default, which is English.
Note:
If the language set for the operating system is not supported by the installer, then by default the installer runs in English.See Also:
Oracle Database Globalization Support Guide for detailed information on character sets and language configurationDetermine your cluster name, public node names, SCAN names, virtual node names, and planned interface use for each node in the cluster
During installation, you are prompted to provide the public and virtual hostname, unless you use a third party cluster software. In that case, the public hostname information will be filled in. You are also prompted to identify which interfaces are public, private, or interfaces in use for another purpose, such as a network file system.
If you use Grid Naming Service (GNS), then OUI displays the public and virtual hostname addresses labeled as "AUTO" because they are configured automatically by GNS.
Note:
If you configure IP addresses manually, then avoid changing host names after you complete the Oracle Grid Infrastructure installation, including adding or deleting domain qualifications. A node with a new hostname is considered a new host, and must be added to the cluster. A node under the old name will appear to be down until it is removed from the cluster.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. This node name can be either the permanent or the virtual host name. The node name should contain only single-byte alphanumeric characters (a to z, A to Z, and 0 to 9). Do not use underscores (_) or any other characters in the hostname.
In addition:
Provide 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 fewer than 15 characters long.
It must consist of the same character set used for host names, in accordance with RFC 1123: Hyphens (-), and single-byte alphanumeric characters (a to z, A to Z, and 0 to 9).
Note:
Windows operating systems allow underscores to be used with hostnames, but underscored names are not legal hostnames for a DNS, and they should be avoided.If you are not using Grid Naming Service (GNS), then 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 Database uses VIPs for client-to-database connections, so the VIP address must be publicly accessible. Oracle recommends that you provide a name in the format hostname-vip. For example: myclstr2-vip.
Provide SCAN addresses for client access to the cluster. These addresses should be configured as round robin addresses on the domain name service (DNS). Oracle recommends that you supply three SCAN addresses.
Note:
The following is a list of additional information about node IP addresses:For the local node only, OUI automatically fills in public and VIP fields. If your system uses vendor clusterware, then OUI may fill additional fields.
Node names are not domain-qualified. If you provide a domain in the host name field during installation, then OUI removes the domain from the name.
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.
Identify public and private interfaces. OUI configures public interfaces for use by public and virtual IP addresses, and configures private IP addresses on private interfaces.
The private subnet that the private interfaces use must connect all the nodes you intend to have as cluster members.
Identify shared storage for Oracle Clusterware files and prepare storage if necessary
During installation, you are asked to provide paths for the following Oracle Clusterware files. These files must be shared across all nodes of the cluster, either on Oracle Automatic Storage Management, or on a supported third party cluster file system:
Voting disks are files that Oracle Clusterware uses to verify cluster node membership and status.
Oracle Cluster Registry files (OCR) contain cluster and database configuration information for Oracle Clusterware.
If you intend to use Oracle Cluster File System (OCFS) for Windows, then you are prompted to indicate which of the available disks you want to format with OCFS for Windows, what format type you want to use, and to what drive letter the formatted OCFS for Windows disk is mounted.
If your file system does not have external storage redundancy, then Oracle recommends that you provide two additional locations for the OCR disk and the voting disk, for a total of at least three partitions. Creating redundant storage locations protects the OCR and voting disk in the event of a failure. To completely protect your cluster, the storage locations given for the copies of the OCR and voting disks should have completely separate paths, controllers, and disks, so that no single point of failure is shared by storage locations.
Disconnect all non-persistent drives
Before starting the Oracle Grid Infrastructure installation on Windows, 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
Have IPMI Configuration completed and have IPMI administrator account information
If you intend to use IPMI, then ensure BMC interfaces are configured, and have an administration account username and password to provide when prompted during installation.
For nonstandard installations, if you must change the configuration on one or more nodes after installation (for example, if you have different administrator usernames and passwords for BMC interfaces on cluster nodes), then decide if you want to reconfigure the BMC interface, or modify IPMI administrator account information after installation as described in Chapter 5, "Oracle Grid Infrastructure Postinstallation Procedures".
Ensure the Oracle home path you select for the grid infrastructure home uses only ASCII characters
At the time of this release, the use of non-ASCII characters for a grid infrastructure home or Oracle Database home is not supported.
This section provides information about how to use Oracle Universal Installer (OUI) to install Oracle Grid Infrastructure. It contains the following sections:
Complete the following steps to install grid infrastructure (Oracle Clusterware and Oracle Automatic Storage Management) on your cluster. You can run OUI from a VNC session, or Terminal Services in console mode.
At any time during installation, if you have a question about what you are being asked to do, then click the Help button on the OUI page.
Log in to Windows using a member of the Administrators group and run the setup.exe command from the Oracle Database 11g Release 2 (11.2) installation media.
Provide information as prompted by OUI. If you need assistance during installation, then click Help. At the end of the installation interview, you can click Details to see the log file.
Note:
If you are upgrading your cluster or part of your cluster from Oracle9i release 2 Cluster Ready Services to Oracle Clusterware 11g, then to ensure backward compatibility, OUI prevents you from changing the cluster name from the existing name by disabling the cluster name field.
To use Oracle9i RAC, you must use Oracle9i Cluster Manager. You can run Oracle9i Cluster Manager on the same server as Oracle Clusterware; however, Oracle Clusterware will manage Oracle Database and Oracle RAC releases 10.1 and higher and Oracle9i Cluster Manager will manage Oracle9i RAC databases.
You cannot use Oracle ASM with Oracle9i Cluster Manager.
After you have specified all the information needed for installation, OUI installs the software then runs the Oracle Net Configuration Assistant, Oracle Private Interconnect Configuration Assistant, and Cluster Verification Utility. These programs run without user intervention.
If you selected to configure Oracle Cluster Registry and voting disk files on Oracle Automatic Storage Management Cluster File System, then the Oracle Automatic Storage Management Configuration Assistant (ASMCA) configures Oracle ASM as part of the installation process. If you did not select Oracle ASM as the storage option for the OCR and voting disk files, then you must start ASMCA manually after installation to configure Oracle ASM.
Start ASMCA using the following command, where Grid_home is the grid infrastructure home:
Grid_home\bin\asmca
When you have verified that your Oracle Grid Infrastructure installation has completed successfully, you can either use it to maintain high availability for other applications, or you can install an Oracle Database software.
If you intend to install Oracle Database 11g release 2 (11.2) with Oracle RAC, then refer to Oracle Real Application Clusters Installation Guide for Microsoft Windows. If you intend to use Oracle Grid Infrastructure on a standalone server (an Oracle Restart deployment), then refer to Oracle Database Installation Guide for Microsoft Windows.
See Also:
Oracle Real Application Clusters Administration and Deployment Guide for information about using cloning and node addition procedures, and Oracle Clusterware Administration and Deployment Guide for cloning Oracle Grid InfrastructureDuring installation of grid infrastructure, 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 node names that it requires to configure the cluster. When creating the text file, save the file with the extension .ccf because the installer only accepts a file of type of Oracle Cluster Configuration File (.ccf).
The cluster configuration file should have the following syntax, where node is the name of the public host name for a node in the cluster, and vip is the virtual IP address for that node:
node vip node vip ...
For example, if have three nodes for your cluster, with host names RACnode1, RACnode2 and RACnode3, you could create a text file named cluster_config.ccf, with the following contents:
RACnode1 RACnode1-vip RACnode2 RACnode2-vip RACnode3 RACnode3-vip
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.
See Also:
Appendix B, "Installing and Configuring Oracle Grid Infrastructure Using Response Files" for more information about using configuration filesComplete the following procedure to perform a noninteractive (silent) installation:
On the installation media, navigate to the directory response.
Using a text editor, open the response file crs_install.rsp. Follow the directions in each section, and supply values appropriate for your environment.
Use the following command syntax to run OUI in silent mode:
setup.exe -silent -reponseFile path_to_your_reponse_file
For example:
E:\ setup.exe -silent -responseFile C:\users\oracle\installGrid.rsp
See Also:
Appendix B, "Installing and Configuring Oracle Grid Infrastructure Using Response Files" for more information about performing silent installations using configuration filesA software-only installation only copies the Oracle Grid Infrastructure for a cluster binaries to the specified node. Configuring Oracle Grid Infrastructure for a cluster and Oracle ASM on all the nodes and then adding the nodes to the cluster must be done manually after the installation has finished.
When you perform a software-only installation of Oracle Grid Infrastructure software, you need to complete several manual configuration steps to enable Oracle Clusterware after you install the software on each node you intend to be a member of the cluster.
Note:
Oracle recommends that only advanced users perform the software-only installation, because this installation method provides no validation of the installation and this installation option requires manual postinstallation steps to enable the grid infrastructure software.If you select a software-only installation, then ensure that the Oracle Grid Infrastructure home path is identical on each cluster member node.
Performing a software-only installation involves the following steps:
Log in to Windows using a member of the Administrators group and run the setup.exe command from the Oracle Database 11g Release 2 (11.2) installation media.
Complete a software-only installation of Oracle Grid Infrastructure for a cluster on the node.
See "Configuring the Software Binaries" for information about configuring Oracle Grid Infrastructure after preforming a software-only installation.
Enable the Oracle RAC option for Oracle Grid infrastructure by renaming the orarac11.dll.dbl file located in the Grid_home\bin directory to orarac11.dll.
Verify that all of the cluster nodes meet the installation requirements using the command runcluvfy.bat stage -pre crsinst -n node_list. Ensure that you have completed all storage and server preinstallation requirements.
Copy the Grid home directory to the same location on the other nodes that you want to configure as cluster member nodes.
On each node that you copied the Grid home to, run the clone.pl script.
Do not run the clone.pl script on the node where you performed the software-only installation.
To configure and activate a software-only grid infrastructure installation for a cluster, complete the following tasks:
Using a text editor, modify the template file Grid_home\crs\install\crsconfig_params for the installer to use to configure the cluster. For example:
... OCR_LOCATIONS=E:\grid\stor1\ocr,F:\grid\stor2\ocr CLUSTER_NAME=racwin-cluster HOST_NAME_LIST=node1,node2,node3,node4 NODE_NAME_LIST=node1,node2,node3,node4 PRIVATE_NAME_LIST= VOTING_DISKS=E:\grid\stor1\vdsk,F:\grid\stor2\vdsk,G:\grid\stor3\vdsk ... CRS_STORAGE_OPTION=2 CSS_LEASEDURATION=400 CRS_NODEVIPS='node1-vip/255.255.255.0/PublicNIC,node2-vip/255.255.255.0/PublicNIC, node3-vip/255.255.255.0/PublicNIC,node4-vip/255.255.255.0/PublicNIC' NODELIST=node1,node2,node3,node4 NETWORKS=192.0.2.1\:public,10.0.0.1\:cluster_interconnect SCAN_NAME=racwin-cluster SCAN_PORT=1521 ... #### Required by OUI add node NEW_HOST_NAME_LIST= NEW_NODE_NAME_LIST= NEW_PRIVATE_NAME_LIST= ...
On all nodes, place the crsconfig_params file in the path Grid_home\crs\install\crsconfig_params, where Grid_home is the path to the Oracle Grid Infrastructure home for a cluster. For example, on node1 you might issue a command similar to the following:
C:> xcopy app\orauser\grid\crs\install\crsconfig_params \\NODE2\app\orauser\grid\crs\install /v
After configuring the crsconfig_params file, run the rootcrs.pl script from the Grid_home on each node, using the following syntax:
Grid_home\perl\lib\perl -IGrid_home\perl\lib -IGrid_home\crs\install Grid_home\crs\install\rootcrs.pl
For example, if your Grid home is C:\app\11.2.0\grid, then you would run the following script:
C:\app\11.2.0\grid\perl\lib\perl -IC:\app\11.2.0\grid\perl\lib -IC:\app \11.2.0\grid\crs\install C:\app\11.2.0\grid\crs\install\rootcrs.pl
Change directory to Grid_home\oui\bin, where Grid_home is the path of the Grid Infrastructure home on each cluster member node.
Enter the following command syntax, where Grid_home is the path of the Grid Infrastructure home on each cluster member node, and node_list is a comma-delimited list of nodes on which you want the software enabled:
setup.exe -updateNodeList ORACLE_HOME=Grid_home -defaultHomeName "CLUSTER_NODES={node_list}" CRS=TRUE
For example:
C:\..\bin> setup.exe -updateNodeList ORACLE_HOME=C:\app\orauser\grid
-defaultHomeName "CLUSTER_NODES={node1,node2,node3,node4}" CRS=TRUE
To enable the Oracle Clusterware installation on the local node only, enter the following command, where Grid_home is the Grid home on the local node, and node_list is a comma-delimited list of nodes on which you want the software enabled:
setup.exe -updateNodeList -local ORACLE_HOME=Grid_home -defaultHomeName "CLUSTER_NODES={node_list}" CRS=TRUE
For example:
C:\..\bin> setup.exe -updateNodeList -local ORACLE_HOME=C:\app\orauser\
grid -defaultHomeName "CLUSTER_NODES={node1,node2,node3,node4}" CRS=TRUE
If you want to configure and activate a software-only grid infrastructure installation for a stand-alone server, then refer to
After installation, log in using a member of the Administrators group, and run the following command from the bin directory in the Grid home to confirm that your Oracle Clusterware installation is installed and running correctly:
crsctl check cluster -all
For example:
C:\..\bin\> crsctl check cluster -all ************************************************************************* node1: CRS-4537: Cluster Ready Services is online CRS-4529: Cluster Synchronization Services is online CRS-4533: Event Manager is online ************************************************************************* node2: CRS-4537: Cluster Ready Services is online CRS-4529: Cluster Synchronization Services is online CRS-4533: Event Manager is online *************************************************************************
If you installed the OCR and voting disk files on Oracle ASM, then run the following command from the Grid_home\bin directory to confirm that your Oracle ASM installation is running:
srvctl status asm
For example:
C:\app\11.2.0\grid\BIN> srvctl status asm ASM is running on node node1 ASM is running on node node2
Oracle ASM is running only if it is needed for Oracle Clusterware files. If you did not configure Oracle Clusterware storage on Oracle ASM during installation, then the Oracle ASM instance should be down.
Note:
To manage Oracle ASM or Oracle Net Services on Oracle Clusterware 11g release 2 (11.2) or later installations, use thesrvctl binary in the Oracle Grid Infrastructure home for a cluster (Grid home). If you have Oracle Real Application Clusters or Oracle Database installed, then you cannot use the srvctl binary in the database home (Oracle home) to manage Oracle ASM or Oracle Net Services.
|
 Copyright © 2007, 2010, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|