PK
:Aoa, mimetypeapplication/epub+zipPK :A iTunesMetadata.plistv
This appendix describes how to perform Oracle Clusterware and Oracle Automatic Storage Management (Oracle ASM) upgrades.
Oracle Clusterware upgrades can be rolling upgrades, in which a subset of nodes are brought down and upgraded while other nodes remain active. Oracle ASM 11g release 2 (11.2) upgrades can be rolling upgrades. If you upgrade a subset of nodes, then a software-only installation is performed on the existing cluster nodes that you do not select for upgrade.
This appendix contains the following topics:
About Oracle ASM and Oracle Grid Infrastructure Installation and Upgrade
Preparing to Upgrade an Existing Oracle Clusterware Installation
Using CVU to Verify System Readiness for Patches and Upgrades
Checking Cluster Health Monitor Repository Size After Upgrading
In past releases, Oracle ASM was installed as part of the Oracle Database installation. With Oracle Database 11g release 2 (11.2), Oracle ASM is installed when you install the Oracle Grid Infrastructure software. Oracle ASM shares an Oracle home with Oracle Clusterware when installed in a cluster such as with Oracle RAC or with Oracle Restart on a standalone server. The directory in which Oracle Clusterware and Oracle ASM is installed is called the Grid home.
If you have an existing Oracle ASM instance, you can either upgrade it at the time that you install Oracle Grid Infrastructure, or you can upgrade it after the installation, using Oracle ASM Configuration Assistant (ASMCA). However, a number of Oracle ASM features are disabled until you upgrade Oracle ASM, and Oracle Clusterware management of Oracle ASM does not function correctly until Oracle ASM is upgraded, because Oracle Clusterware only manages Oracle ASM when it is running in the Oracle Grid Infrastructure home. For this reason, Oracle recommends that if you do not upgrade Oracle ASM at the same time as you upgrade Oracle Clusterware, then you should upgrade Oracle ASM immediately afterward.
You can perform out-of-place upgrades to an Oracle ASM instance using ASMCA. In addition to running ASMCA using the graphic user interface (GUI), you can run ASMCA in non-interactive (silent) mode.
In earlier releases, you could use Database Upgrade Assistant (DBUA) to upgrade either an Oracle Database, or Oracle ASM. With Oracle Database 11g release 2 (11.2), you can use DBUA to upgrade only an Oracle Database instance. To upgrade Oracle ASM separately, you use ASMCA.
See Also: Oracle Database Upgrade Guide and Oracle Automatic Storage Management Administrator's Guide for additional information about upgrading existing Oracle ASM installations |
Be aware of the following restrictions and changes for upgrades to Oracle Grid Infrastructure installations, which consists of Oracle Clusterware and Oracle ASM.
To upgrade existing Oracle Clusterware installations to Oracle Grid Infrastructure 11g, your current release must be at least 10.1.0.3, 10.2.0.3, 11.1.0.6, or 11.2.
To upgrade existing Oracle ASM installations to Oracle Grid Infrastructure 11g release 2 (11.2) using the rolling upgrade method, your current release must be at least 11.1.0.6.
To upgrade Oracle Grid Infrastructure release 11.2.0.1 to Oracle Grid Infrastructure release 11.2.0.2, you must first do at least one of the following:
Patch the Oracle Grid Infrastructure release 11.2.0.1 home with the patch for bugs 9413827 (9978481) and 9706490 (10047003).
Install the latest bundle for the cumulative patches for Oracle Grid Infrastructure (Patch 11 bundle or higher).
Adding nodes to a cluster during a rolling upgrade is not supported.
Oracle Clusterware and Oracle ASM upgrades are always out-of-place upgrades. With Oracle Grid Infrastructure 11g release 2 (11.2), you cannot perform an in-place upgrade of Oracle Clusterware and Oracle ASM to existing homes.
With Oracle Clusterware 11g release 1 and later releases, the same user that owned the Oracle Clusterware 10g software must perform the Oracle Clusterware 11g upgrade. Before the Oracle Database 11g release, either all Oracle software installations were owned by a single user, typically oracle
, or Oracle Database software was owned by oracle
, and Oracle Clusterware software was owned by a separate user, typically crs
.
If the existing Oracle Clusterware home is a shared home, you can use a non-shared home for the Oracle Grid Infrastructure for a Cluster home for Oracle Clusterware and Oracle ASM 11g release 2 (11.2).
Oracle ASM and Oracle Clusterware both run in the Oracle Grid Infrastructure home.
During a major version upgrade to Oracle Clusterware 11g release 2 (11.2), the software in the Grid home for Oracle Grid Infrastructure 11g release 2 (11.2) is not fully functional until the upgrade is completed. Running the Server Control Utility (SRVCTL), crsctl
, and other commands from the 11g release 2 (11.2) Grid home is not supported until the upgrade is complete across all nodes.
To manage pre-existing databases using earlier versions (release 10.x or 11.1) of Oracle Database software during the Oracle Grid Infrastructure upgrade, use SRVCTL in the existing database homes.
Oracle Clusterware upgrades can be rolling upgrades, in which a subset of nodes are brought down and upgraded while other nodes remain active. Oracle ASM 11g release 2 (11.2) upgrades can be rolling upgrades. If you upgrade a subset of nodes, then a software-only installation is performed on the existing cluster nodes that you do not select for upgrade. Rolling upgrades avoid downtime and ensure continuous availability while the software is upgraded to a new version.
Note: In contrast with releases prior to Oracle Clusterware 11g release 2, Oracle Universal Installer (OUI) always performs rolling upgrades, even if you select all nodes for the upgrade. |
During an out-of-place upgrade, the installer installs the newer version in a separate Oracle Clusterware home. Both versions of Oracle Clusterware are on each cluster member node, but only one version is active. By contrast, an in-place upgrade overwrites the software in the current Oracle Clusterware home.
To perform an out-of-place upgrade, you must create new Oracle Grid Infrastructure homes on each node. Then you can perform an out-of-place rolling upgrade, so that some nodes are running Oracle Clusterware from the original Oracle Clusterware home, and other nodes are running Oracle Clusterware from the new Oracle Grid Infrastructure home.
If you have an existing Oracle Clusterware installation, then you upgrade your existing cluster by performing an out-of-place upgrade. An in-place upgrade of Oracle Clusterware 11g release 2 is not supported.
See Also: "Performing a Rolling Upgrade of Oracle Clusterware" for instructions on completing rolling upgrades |
If you have an existing Oracle Clusterware installation, then you upgrade your existing cluster by performing an out-of-place upgrade. You cannot perform an in-place upgrade. The following sections describe the tasks you should complete before starting an upgrade:
If you are completing a patch update of Oracle Clusterware or Oracle ASM, then after you download the patch software and before you start to patch or upgrade your software installation, review the Patch Set Release Notes that accompany the patch to determine if your system meets the system requirements for the operating system and the hardware.
Use the Cluster Verification Utility (CVU) to assist you with system checks in preparation for patching or upgrading. You can run CVU before starting the upgrade, however, the installer runs the appropriate CVU checks automatically, and prompts you to fix problems before proceeding with the upgrade.
Ensure that you have the information you will need when installation Oracle Grid Infrastructure into a new home directory, including the following:
The Oracle home location for the current Oracle Clusterware installation.
With Oracle Clusterware 11g release 2 (11.2), you can perform upgrades on a shared Oracle Clusterware home.
An Oracle Grid Infrastructure home location that is different from your existing Oracle Clusterware home or Grid home location
A single client access name (SCAN) address
Local Administrator user access, or access as the user who performed the previous Oracle Clusterware installation
If your current Oracle Clusterware installation is not currently running at least the minimum supported version for that release (10.1.0.3, 10.2.0.3, 11.1.0.6, or 11.2), then a prerequisite check failure is reported. You must upgrade your current Oracle Clusterware installation to at least the minimum supported version for that release before upgrading. For example, if you plan to upgrade your Oracle Clusterware 10g release 1 installation to Oracle Clusterware 11g release 2 (11.2) and your current Oracle Clusterware installation is version 10.1.0.2, then you must upgrade your current Oracle Clusterware installation to version 10.1.0.3 or higher before starting the upgrade
If you have had an existing installation on your system, and you are using the same user account to install this installation, then unset the following environment variables, and any other environment variable set for the Oracle installation user that is connected with Oracle software homes.
ORACLE_HOME
ORACLE_SID
ORA_NLS10
TNS_ADMIN
ORA_CRS_HOME
If you have set ORA_CRS_HOME
as an environment variable, following instructions from Oracle Support, then unset it before starting an installation or upgrade. You should never use ORA_CRS_HOME
as an environment variable except under explicit direction from Oracle Support.
To remove the environment variable settings for all sessions, from the Start menu, right click My Computer and select Properties. In the System Properties window, select Advanced, then click the Environment Variables button.
Also, check to ensure that the user profile for the installation owner does not set any of these environment variables.
If you are completing a patch update of Oracle Clusterware or Oracle ASM, then after you download the patch software and before you start to patch or upgrade your software installation, review the Patch Set Release Notes that accompany the patch to determine if your system meets the system requirements for the operating system and the hardware.
Navigate to the staging area for the upgrade, where the runcluvfy
command is located, and run the command runcluvfy stage -pre crsinst -upgrade
to check the readiness of your Oracle Clusterware installation for upgrades. Running runcluvfy with the -pre crsinst -upgrade
flags performs system checks to confirm if the cluster is in a correct state for upgrading from an existing clusterware installation.
The command uses the following syntax, where variable content is indicated by italics:
runcluvfy stage -pre crsinst -upgrade [-n node_list] [-rolling] -src_crshome src_Gridhome -dest_crshome dest_Gridhome -dest_version dest_version [-fixup[-fixupdir fixupdirpath]] [-verbose]
The options used in this command are:
-n nodelist | The -n flag indicates cluster member nodes, and nodelist is the comma-delimited list of non-domain qualified node names on which you want to run a preupgrade verification. If you do not add the -n flag to the verification command, then all the nodes in the cluster are verified. |
-rolling | Use this flag to verify readiness for rolling upgrades. |
-src_crshome src_Gridhome | Use this flag to indicate the location of the source Oracle Clusterware or Grid home that you are upgrading, where src_Gridhome is the path to the home that you want to upgrade. |
-dest_crshome dest_Gridhome | Use this flag to indicate the location of the upgrade Grid home, where dest_Gridhome is the path to the Grid home. |
-dest_version dest_version | Use the dest_version flag to indicate the release number of the upgrade, including any Patch set. The release number must include the five digits designating the release to the level of the platform-specific patch. For example: 11.2.0.2.0. |
-fixup [-fixupdir fixupdirpath ] | (Linux and UNIX) Use the -fixup flag to indicate that you want to generate instructions for any required steps you need to complete to ensure that your cluster is ready for an upgrade. The default location is the CVU work directory. If you want to place the fixup instructions in a different directory, then add the flag -fixupdir , and provide the path to the fixup directory |
-verbose | Use the -verbose flag to produce detailed output of individual checks |
Use the Cluster Verification Utility (CVU) to assist you with system checks in preparation for patching or upgrading. You can run CVU before starting the upgrade, however, the installer runs the appropriate CVU checks automatically, and prompts you to fix problems before proceeding with the upgrade.
Example D-1 Using CVU to Verify System Upgrade Readiness for Grid Infrastructure
You can verify that the permissions required for installing Oracle Clusterware have been configured on the nodes node1 and node2 by running the following command:
C:\stage> runcluvfy.bat stage -pre crsinst -upgrade -n node1,node2 -rolling -src_crshome C:\app\11.2.0\grid -dest_crshome C:\app\11.2.0.3\grid -dest_version 11.2.0.3.0 -fixup -fixupdirpath C:\user\grid\fixup -verbose
Before you make any changes to the Oracle software, Oracle recommends that you create a backup of the Oracle software and databases.
Use the following procedure to upgrade Oracle Clusterware from an earlier release to Oracle Clusterware 11g release 2. You can also choose to upgrade Oracle ASM during the upgrade of Oracle Clusterware.
If there are non-clustered, or single-instance, Oracle databases that use Oracle ASM running on any of the nodes in the cluster, they must be shut down before you start the upgrade. Listeners associated with those databases do not have to be shut down.
Note: Oracle recommends that you leave Oracle Real Application Clusters (Oracle RAC) instances running during the Oracle Clusterware upgrade. During the upgrade process, the database instances on the node being upgraded are stopped and started automatically during the upgrade process. |
Stop the Enterprise Manager Database Control on each node. Run the following command to stop Database Control:
C:\> emctl stop dbconsole
Start the installer, and select the option to upgrade an existing Oracle Clusterware and Oracle ASM installation.
On the node selection page, select all nodes.
Note: In contrast with releases prior to Oracle Clusterware 11g release 2, all upgrades are rolling upgrades, even if you select all nodes for the upgrade. If you are upgrading from Oracle Clusterware 11g release 11.2.0.1 to release 11.2.0.2, then all nodes are selected by default. You cannot select or de-select the nodes. |
Select installation options as prompted.
If prompted to do so, run the scripts as directed.
When the Oracle Clusterware upgrade is complete, if an earlier version of Oracle ASM is installed, then the installer starts ASMCA to upgrade Oracle ASM to release 11.2. You can upgrade Oracle ASM at this time, or upgrade it later.
Oracle recommends that you upgrade Oracle ASM at the same time that you upgrade Oracle Clusterware. Until Oracle ASM is upgraded, Oracle databases that use Oracle ASM cannot be created. Until Oracle ASM is upgraded, the Oracle ASM management tools in the Oracle Grid Infrastructure 11g release 2 (11.2) home (for example, SRVCTL) will not work.
Note: After the upgrade, if you set the Oracle Cluster Registry (OCR) backup location manually to the earlier release Oracle Clusterware home (CRS home), then you must change the OCR backup location to the Oracle Grid Infrastructure home (Grid home). If you did not set the OCR backup location manually, then this issue does not concern you.Because upgrades of Oracle Clusterware are out-of-place upgrades, the CRS home for the earlier release Oracle Clusterware cannot be the location of the OCR backups for Oracle Clusterware 11g release 2. Backups in the old Oracle Clusterware home could be deleted. |
After you have completed the Oracle Clusterware 11g release 2 (11.2) upgrade, if you did not choose to upgrade Oracle ASM when you upgraded Oracle Clusterware, then you can do it separately using ASMCA to perform rolling upgrades.
You can use ASMCA to complete the upgrade of Oracle ASM separately, but you should perform the upgrade as soon as possible after you upgrade Oracle Clusterware, because Oracle ASM management tools such as SRVCTL will not work until Oracle ASM is upgraded.
Note: ASMCA performs a rolling upgrade only if the earlier version of Oracle ASM is either 11.1.0.6 or 11.1.0.7. Otherwise, ASMCA performs a normal upgrade, during which ASMCA shuts down all Oracle ASM instances on all nodes of the cluster, and then starts an Oracle ASM instance on each node from the new Oracle Grid Infrastructure home. |
Note the following if you intend to perform rolling upgrades of Oracle ASM:
The active version of Oracle Clusterware must be 11g release 2 (11.2). To determine the active version, enter the following command from the Grid home:
C:\..\bin> crsctl query crs activeversion
You can upgrade a single instance Oracle ASM installation to a clustered Oracle ASM installation. However, you can only upgrade an existing single instance Oracle ASM installaD5tion if you run the installation from the node on which the Oracle ASM installation is installed. You cannot upgrade a single instance Oracle ASM installation on a remote node.
You must ensure that any rebalance operations on your existing Oracle ASM installation are completed before starting the upgrade.
During the upgrade, you alter the state of the Oracle ASM instances to an upgrade state. Because this upgrade state limits Oracle ASM operations, you should complete the upgrade soon after you begin. The following operations are allowed when an Oracle ASM instance is in the upgrade state:
Diskgroup mounts and dismounts
Opening, closing, resizing, or deleting database files
Recovering instances
Queries of fixed views and packages: Users are allowed to query fixed views and run anonymous PL/SQL blocks using fixed packages, such as DBMS_DISKGROUP
)
Complete the following procedure to upgrade Oracle ASM:
On the node on which you plan to start the upgrade, set the environment variable ASMCA_ROLLING_UPGRADE
to true
to put the Oracle ASM instance in an upgrade state, for example:
C:\> set ASMCA_ROLLING_UPGRADE=true
From the Oracle Grid Infrastructure 11g release 2 (11.2) home, start ASMCA, as shown in the following example, where C:\app\11.2.0\grid
is the Grid home:
C:\> cd app\11.2.0\grid\bin C:\..\bin> asmca.bat
Select Upgrade.
ASMCA upgrades Oracle ASM in succession for all nodes in the cluster.
When the upgrade is complete for all the nodes, unset the environment variable ASMCA_ROLLING_UPGRADE
:
C:\> set ASMCA_ROLLING_UPGRADE=
See Also: Oracle Database Upgrade Guide and Oracle Automatic Storage Management Administrator's Guide for additional information about preparing an upgrade plan for Oracle ASM, and for starting, completing, and stopping Oracle ASM upgrades |
Because Oracle Clusterware 11g release 2 (11.2) is an out-of-place upgrade, the upgraded software has a new location for the Grid home. The path for the Oracle Clusterware home in some Oracle Enterprise Manager parameter files must be changed. If you do not change the parameter, then you will encounter errors such as "cluster target broken" on Oracle Enterprise Manager Database Control or Grid Control.
Use the following procedure to resolve this issue:
Log in to Database Control or Grid Control.
Select the Cluster tab.
Click Monitoring Configuration.
Update the value for Oracle Home with the new path for the Grid home.
If you are upgrading from a prior release using IPD/OS to Oracle Grid Infrastructure release 2 (11.2.0.3), then you should review the Cluster Health Monitor repository size (the CHM repository). Oracle recommends that you review your CHM repository needs, and enlarge the repository size if you want to maintain a larger CHM repository.
Note: Your previous IPD/OS repository is deleted when you install Oracle Grid Infrastructure. |
By default, the CHM repository size for release 11.2.0.3 and later is a minimum of either 1GB or 3600 seconds (1 hour).
To enlarge the CHM repository, use the following command syntax, where RETENTION_TIME is the size of CHM repository in number of seconds:
oclumon manage -repos resize RETENTION_TIME
The value for RETENTION_TIME must be more than 3600
(one hour) and less than 259200
(three days). If you enlarge the CHM repository size, then you must ensure that there is local space available for the repository size you select on each node of the cluster. If there is not sufficient space available, then you can move the repository to shared storage.
For example, to set the repository size to four hours:
C:\> oclumon manage -repos resize 14400
This section describes some commonly encountered problems during the upgrade process.
emctl stop dbconsole
. Check to ensure other Oracle processes from the earlier release software are stopped.After a successful or a failed upgrade to Oracle Clusterware 11g release 2 (11.2), you can restore Oracle Clusterware to the previous version.
The restoration procedure in this section restores the Oracle Clusterware configuration to the state it was in before the Oracle Clusterware 11g release 2 upgrade. Any configuration changes you performed during or after the upgrade are removed and cannot be recovered.
In the following procedure, the local node is the first node on which the rootupgrade script was run. The remote nodes are all other nodes that were upgraded.
To restore Oracle Clusterware to the earlier release:
Use the downgrade procedure for the release to which you want to downgrade.
Downgrading to releases prior to 11g release 2 (11.2.0.1):
On all remote nodes, use the command Grid_home
\crs\install\rootcrs.pl
-downgrade [-force]
to stop the Oracle Clusterware 11g release 2 resources and shut down the Oracle Clusterware stack.
For example:
C:\app\11.2.0\grid\crs\install> rootcrs.pl -downgrade
To stop a partial or failed Oracle Clusterware 11g release 2 upgrade and restore Oracle Clusterware to the previous release, use the -force
flag with this command.
Downgrading to releases 11.2.0.1 or later:
Use the command syntax rootcrs.pl -downgrade
-
oldcrshome
oldGridHomePath
-version
oldGridversion
, where oldGridhomepath
is the path to the previous release Oracle Grid Infrastructure home, and oldGridversion
is the release to which you want to downgrade. For example:
rootcrs.pl -downgrade -oldcrshome C:\app\11.2.0\grid -version 11.2.0.1.0
If you want to stop a partial or failed 11g release 2 (11.2) installation and restore the previous release of Oracle Clusterware, then use the -force
flag with this command.
After the rootcrs.pl -downgrade
script has completed on all remote nodes, on the local node use the command Grid_home
\crs\install\rootcrs.p
l -downgrade -lastnode -oldcrshome
pre11.2_crs_home
-version
pre11.2_crs_version
[-force]
, where pre11.2_crs_home
is the home of the earlier Oracle Clusterware installation, and pre11.2_crs_version
is the release number of the earlier Oracle Clusterware installation.
For example:
C:\app\11.2.0.3\grid\crs\install> rootcrs.pl -downgrade -lastnode -oldcrshome C:\app\11g\crs -version 11.1.0.6.0
This script downgrades the OCR. If you want to stop a partial or failed 11g release 2 (11.2) installation and restore the previous release Oracle Clusterware, then use the -force
flag with this command.
Log in as the Grid Infrastructure installation owner and run the following commands, where C:\app\11.2.0\grid
is the location of the new Grid home (11.2):
setup.exe -nowait -waitforcompletion -ignoreSysPrereqs -updateNodeList -silent CRS=false ORACLE_HOME=C:\app\11.2.0\grid
Append -cfs
to the end of the above command is the Oracle Grid home is a shared home.
As the Grid infrastructure installation owner, run the following command, where C:\app\crs
represents the home directory of the earlier Oracle Clusterware installation, for example:
setup.exe -nowait -waitforcompletion -ignoreSysPrereqs -updateNodeList -silent CRS=true ORACLE_HOME=C:\app\crs
Append -cfs
to the end of the above command is the Oracle Clusterware home is a shared home.
For 11.2.0.3 and later releases
On each node, start Oracle Clusterware from the earlier release Oracle Clusterware home using the command crsctl start crs
. For example, where the earlier release home is C:\app\crs
, use the following command on each node:
C:\app\crs\bin> crsctl start crs
For 11.2.0.2 and earlier releases
You are prompted to run root.bat
from the earlier release Oracle Clusterware installation home in sequence on each member node of the cluster. After you complete this task, downgrade is completed.
Running root.bat
from the earlier release Oracle Clusterware installation home restarts the Oracle Clusterware stack, starts up all the resources previously registered with Oracle Clusterware in the older version, and configures the old initialization scripts to run the earlier release Oracle Clusterware stack.
This section describes new features as they pertain to the installation and configuration of Oracle Grid Infrastructure (Oracle Clusterware and Oracle Automatic Storage Management) on Microsoft Windows platforms. This guide replaces Oracle Clusterware Installation Guide. The topics in this section are:
New Features for Oracle Grid Infrastructure 11g Release 2 (11.2.0.3)
New Features for Oracle Grid Infrastructure 11g Release 2 (11.2.0.2)
New Features for Oracle Grid Infrastructure 11g Release 2 (11.2)
Note the following:
With this release, Oracle Universal Installer (OUI) no longer supports installation of Oracle Clusterware files on raw devices. Install Oracle Clusterware files either on Oracle Automatic Storage Management (Oracle ASM) disk groups, or in a supported shared file system.
The following is a list of new features are available starting with Oracle Grid Infrastructure 11g release 2 (11.2.0.3):
Cluster Health Monitor gathers operating system metrics in real time, and stores them in its repository for later analysis, so that it can determine the root cause of many Oracle Clusterware and Oracle RAC issues with the assistance of Oracle Support.
Cluster Health Monitor also works in conjunction with Oracle Database Quality of Service Management (QoS) by providing metrics to detect memory over-commitment on a node. QoS Management can shut down services on overloaded nodes to relieve stress, to and preserve existing workloads.
To support QoS Management, Oracle Database Resource Manager and metrics have been enhanced to support fine-grained performance metrics, and also can manage workloads with user-defined performance classes.
The Database Quality of Service (QoS) Management Server allows system administrators to manage application service levels hosted in Oracle Database clusters by correlating accurate run-time performance and resource metrics and analyzing with an expert system to produce recommended resource adjustments to meet policy-based performance objectives.
The following is a list of new features are available starting with Oracle Grid Infrastructure 11g release 2 (11.2.0.2):
Oracle Grid Infrastructure patch sets are full installations of the Oracle Grid Infrastructure software. Note the following changes with the new patch set packaging:
Direct upgrades from previous releases (11.x, 10.2.x) to the most recent patch set are supported.
Out-of-place patch set upgrades only are supported. An out-of-place upgrade is one in which you install the patch set into a new, separate home.
New installations consist of installing the most recent patch set, rather than installing a base release and then upgrading to a patch release.
See Also: My Oracle Support Doc ID 1189783.1, "Important Changes to Oracle Database Patch Sets Starting With 11.2.0.2", available from the following URL: |
Use the Software Updates feature to dynamically download and apply software updates as part of the Oracle Database installation. You can also download the updates separately using the downloadUpdates
option and later apply them during the installation by providing the location where the updates are present.
The installation of Oracle Grid Infrastructure for a Cluster with Oracle Database 11g Release 2 includes a software-only option. The Configuration wizard assists the administrator with completing the cluster configuration independently of the software installation. You no longer have to manually edit the config_params
configuration file as this wizard takes you through the process, step by step.
The following is a list of new features for installation of Oracle Clusterware and Oracle ASM 11g release 2 (11.2):
With Oracle Grid Infrastructure 11g release 2 (11.2), Oracle ASM and Oracle Clusterware are installed into a single home directory, which is referred to as the Grid home. Configuration assistants start after the installer interview process that configures Oracle ASM and Oracle Clusterware.
The installation of the combined products is called Oracle Grid Infrastructure. However, Oracle Clusterware and Oracle ASM remain separate products.
With this release, Oracle Cluster Registry (OCR) and voting disks can be placed on Oracle ASM.
This feature enables Oracle ASM to provide a unified storage solution, storing all the data for the clusterware and the database, without the need for third-party volume managers or cluster filesystems.
For new installations, OCR and voting disk files can be placed either on Oracle ASM, or on a cluster file system. Installing Oracle Clusterware files on raw devices is no longer supported, unless an existing system is being upgraded.
Oracle Automatic Storage Management Cluster File System (Oracle ACFS) is a new multi-platform, scalable file system and storage management design that extends Oracle ASM technology to support all application data. Oracle ACFS provides dynamic file system resizing, and improved performance using the distribution, balancing and striping technology across all available disks, and provides storage reliability through the mirroring and parity protection Oracle ASM provides.
Note: For Oracle ASM 11g release 2 (11.2.0.1), Oracle ACFS is supported on only Windows Server 2003 64-bit and Windows Server 2003 R2 64-bit. Oracle ACFS is also supported on Windows Server 2008, x64 and Windows Server 2008 R2, x64 starting with Oracle Database 11g Release 2 (11.2.0.2). |
Cluster node times should be synchronized. With this release, Oracle Clusterware provides Cluster Time Synchronization Service (CTSS), which ensures that there is a synchronization service in the cluster. If Network Time Protocol (NTP) or Windows Time Service is not found during cluster configuration, then CTSS is configured to ensure time synchronization.
Oracle Enterprise Manager Database Control 11g provides the capability to automatically provision Oracle Grid Infrastructure and Oracle RAC installations on new nodes, and then extend the existing Oracle Grid Infrastructure and Oracle RAC database to these provisioned nodes. This provisioning procedure requires a successful Oracle RAC installation before you can use this feature.
See Also: Oracle Real Application Clusters Administration and Deployment Guide for information about this feature |
In the past, adding or removing servers in a cluster required extensive manual preparation. With this release, you can continue to configure server nodes manually, or use Grid Plug and Play to configure them dynamically as nodes are added or removed from the cluster.
Grid Plug and Play reduces the costs of installing, configuring, and managing server nodes by starting a grid naming service within the cluster to allow each node to perform the following tasks dynamically:
Negotiating appropriate network identities for itself
Acquiring additional information it needs to operate from a configuration profile
Configuring or reconfiguring itself using profile data, making host names and addresses resolvable on the network
Because servers perform these tasks dynamically, the number of steps required to add or delete nodes is minimized.
Oracle Clusterware 11g release 2 (11.2) replaces the oprocd
process with the Cluster Synchronization Service (CSS) Agent and Monitor to provide more accurate recognition of hangs and to avoid false termination.
Intelligent Platform Management Interface (IPMI) is an industry standard management protocol that is included with many servers today. IPMI operates independently of the operating system, and can operate even if the system is not powered on. Servers with IPMI contain a baseboard management controller (BMC) which is used to communicate to the server.
If IPMI is configured, then Oracle Clusterware uses IPMI when node fencing is required and the server is not responding.
With this release, you can install a new version of Oracle Clusterware into a separate home from an existing Oracle Clusterware installation. This feature reduces the downtime required to upgrade a node in the cluster. When performing an out-of-place upgrade, the old and new version of the software are present on the nodes at the same time, each in a different home location, but only one version of the software is active.
With this release, you can use the Oracle Enterprise Manager Cluster Home page to perform full administrative and monitoring support for both standalone database and Oracle RAC environments, using High Availability Application and Oracle Cluster Resource Management.
When Oracle Enterprise Manager is installed with Oracle Clusterware, it can provide a set of users that have the Oracle Clusterware Administrator role in Oracle Enterprise Manager, and provide full administrative and monitoring support for High Availability application and Oracle Clusterware resource management. After you have completed the installation and deployed Oracle Enterprise Manager, you can provision nodes added to the cluster using Oracle Enterprise Manager.
With this release, the Single Client Access Name (SCAN) is the host name to provide for all clients connecting to the cluster. SCAN is a domain name registered to at least one and up to three IP addresses, either in the domain name service (DNS) or the Grid Naming Service (GNS). SCAN eliminates the need to change clients when nodes are added to or removed from the cluster. Clients using SCAN can also access the cluster using the Easy Connect Naming Method.
With this release, you can use the Server Control utility (SRVCTL) to shut down all Oracle software running within an Oracle home, in preparation for patching. Oracle Grid Infrastructure patching is automated across all nodes, and patches can be applied in a multi-node, multi-patch fashion.
To streamline cluster installations, especially for those customers who are new to clustering, Oracle introduces the Typical Installation path. Typical installation defaults as many options as possible to those recommended as best practices.
OUI no longer removes Oracle software. Use the new Deinstallation tool (deinstall.bat
) available on the installation media before installation and in the Oracle home directory after installation. The Deinstallation tool can also be downloaded from Oracle Technology Network.
In prior releases, backing up the voting disks was a required postinstallation task. With Oracle Clusterware release 11.2 and later, backing up and restoring a voting disk is not supported.
Backing up voting disks manually is no longer required, because voting disks are backed up automatically in the OCR as part of any configuration change. Voting disk data is automatically restored to any added voting disks.
The following is a list of new features for Oracle Clusterware 11g release 1 (11.1)
With Oracle Database 11g release 1, Oracle Clusterware can be installed or configured as an independent product, and additional documentation is provided on storage administration. For installation planning, note the following documentation:
This book provides an overview and examples of the procedures to install and configure a two-node Oracle Clusterware and Oracle RAC environment.
This book (the guide that you are reading) provides procedures either to install Oracle Clusterware as a standalone product, or to install Oracle Clusterware with either Oracle Database, or Oracle RAC. It contains system configuration instructions that require system administrator privileges.
This platform-specific book provides procedures to install Oracle RAC after you have completed an Oracle Clusterware installation. It contains database configuration instructions for database administrators.
This book provides information for database and storage administrators who administer and manage storage, or who configure and administer Oracle ASM.
This is the administrator's reference for Oracle Clusterware. It contains information about administrative tasks, including those that involve changes to operating system configurations and cloning Oracle Clusterware.
This is the administrator's reference for Oracle RAC. It contains information about administrative tasks. These tasks include database cloning, node addition and deletion, Oracle Cluster Registry (OCR) administration, use of SRVCTL and other database administration utilities, and tuning changes to operating system configurations.
The following is a list of enhancements and new features for Oracle Database 11g release 1 (11.1):
This feature introduces a new SYSASM privilege that is specifically intended for performing Oracle ASM administration tasks. Using the SYSASM privilege when connecting to Oracle ASM instead of the SYSDBA privilege provides a clearer division of responsibility between Oracle ASM administration and database administration.
Installation Guide
11g Release 2 (11.2) for Microsoft Windows x64 (64-Bit)
E24169-04
May 2012
Oracle Grid Infrastructure Installation Guide, 11g Release 2 (11.2) for Microsoft Windows x64 (64-Bit)
E24169-04
Copyright © 2007, 2012, Oracle and/or its affiliates. All rights reserved.
Primary Authors: Janet Stern, Douglas Williams
Contributing Authors: Mark Bauer, Jonathan Creighton, Reema Khosla, Barb Lundhild, Saar Maoz, Markus Michalewicz, Philip Newlan, Hanlin Qian
Contributors: Karin Brandauer, Barbara Glover, Sujatha Srinivasa Gopalan, Shivanand Hiremath, Yingwei Hu, Wei Huang, Scott Jesse, Sameer Joshi, Alexander Keh, Jai Krishnani, Jifeng Liu, Fangya Lu, Anil Nair, Mohammed Shahnawaz Quadri, Sudhe Sampath, Vishal Saxena, Janelle Simmons, Malaiarasan Stalin, Richard Strohm, Preethi Subramanyam, Preethi Vallam, Zhiqiang Yang
This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.
The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.
If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable:
U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, duplication, disclosure, modification, and adaptation shall be subject to the restrictions and license terms set forth in the applicable Government contract, and, to the extent applicable by the terms of the Government contract, the additional rights set forth in FAR 52.227-19, Commercial Computer Software License (December 2007). Oracle America, Inc., 500 Oracle Parkway, Redwood City, CA 94065.
This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.
Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.
This software or hardware and documentation may provide access to or information on content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services.
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:
Preparing to Install Oracle Grid Infrastructure with Oracle Universal Installer
Installing Oracle Grid Infrastructure Using a Software-Only Installation
Understanding Offline Processes in Oracle Grid Infrastructure
Note: The second phase of an Oracle RAC installation, installing Oracle RAC, is described in Oracle Real Application Clusters Installation Guide for Microsoft Windows x64 (64-Bit). |
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. Check off each task in the following list as you complete it, and write down the information needed, so that you can provide it during installation.
Verify Cluster Privileges
Before running OUI, 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 a Local 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, where nodename
is the node name:
net use \\nodename\C$
Repeat for each node in the cluster.
Shut Down Running Oracle Processes
You may have to shut down running Oracle processes:
Installing on a node with a standalone database not using Oracle ASM: You do not have to shut down the database while you install Oracle Grid Infrastructure software.
Installing on a node that already has a standalone Oracle Database 11g release 2 (11.2) installation running on Oracle ASM: Stop the existing Oracle ASM instances. The Oracle ASM instances are restarted during installation.
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.
Prepare for Oracle ASM and Oracle Clusterware upgrade if you have existing installations
During the installation of Oracle Grid Infrastructure, existing Oracle Clusterware and clustered Oracle ASM installations are upgraded.
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 as a Local 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 OUI, then OUI, by default, runs in English. |
See Also: Oracle Database Globalization Support Guide for detailed information on character sets and language configuration |
Determine your cluster name, public node names, single client access name (SCAN), virtual node names, GNS VIP, and planned interface use for each node in the cluster
During installation, you are prompted to provide the public and virtual host name, unless you use a third party cluster software. In that case, the public host name 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 host name addresses labeled as "AUTO" because they are configured automatically by GNS.
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 host name.
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 less than 15 characters long.
It must consist of the same character set used for host names, in accordance with Internet Engineering Task Force 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 in host names. However, because underscored names are not legal host names for a domain name system (DNS), they should be avoided. |
If you are not using 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 virtual IP (VIP) addresses 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:
|
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.
Obtain proxy realm authentication information if you have a proxy realm on your network
During installation, OUI attempts to download updates. You are prompted to provide a proxy realm, and user authentication information to access the Internet through the proxy service. If you have a proxy realm configured, then be prepared to provide this information. If you do not have a proxy realm, then you can leave the proxy authentication fields blank.
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 ASM, or on a supported 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 for Windows (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 voting disks, for a total of at least three partitions. If the OCR and voting disks are not stored together, then you will need at least six partitions (three for the OCR and three for voting disks). Creating redundant storage locations protects the OCR and voting disk if a failure occurs. 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.
When you select to store the OCR on Oracle ASM, the default configuration is to create the OCR in one Oracle ASM disk group. If you create the disk group with normal or high redundancy, then the OCR is protected from physical disk failure.
To protect the OCR from logical disk failure, create another Oracle ASM disk group after installation and add the OCR to the second disk group using the ocrconfig
command.
See Also: |
Disconnect all non-persistent drives
Before starting the Oracle Grid Infrastructure installation on Windows, ensure that you disconnect all nonpersistent drives that are temporarily mounted on all the nodes. Alternatively, to access the shared drive, make the shared drive persistent using the following command:
net use * \\servername\sharename /persistent: YES
Disable Anti-Virus software
Disable any anti-virus software running on cluster nodes before and for the entire duration of the Oracle Grid Infrastructure 11g release 2 installation. If the system is restarted before the installation is complete, ensure the anti-virus software was not restarted before continuing with the installation. Anti-virus software can be re-enabled when the installation is complete.
Have intelligent platform management interface (IPMI) configuration completed and have IPMI administrator account information
If you intend to use IPMI, then ensure baseboard management controller (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 that the Oracle home path you select for the Grid home uses only American standard code for information interchange (ASCII) characters
The use of non-ASCII characters in any part of the path for an Oracle Grid Infrastructure home (Grid home) or Oracle Database home is not supported. This restriction includes installation owner user names, which are used as a default for some home paths, as well as other directory names you may select for paths.
Unset Oracle environment variables. If you have set ORA_CRS_HOME
as an environment variable, then unset it before starting an installation or upgrade. You should never configure ORA_CRS_HOME
as a user or system environment variable.
If you have had an existing installation on your system, and you are using the same user account to install this installation, then unset the following environment variables: ORA_CRS_HOME
; ORACLE_HOME
; ORA_NLS10
; TNS_ADMIN
Decide if you want to use the Software Updates option. OUI can install critical patch updates and system requirements updates for supported operating systems, and other significant updates that can help to ensure your installation proceeds smoothly. Oracle recommends that you enable software updates during installation.
If you choose to enable software updates, then during installation you must provide a valid My Oracle Support user name and password, so that OUI can download the latest updates, or you must provide a path to the location of an software updates packages that you have downloaded previously.
If you plan to run the installation in a secured data center, then you can download updates before starting the installation by starting OUI in update download mode on a system that has Internet access. To start OUI to download updates, enter the following command from the base directory of the installation media:
X:\> setup.exe -downloadUpdates
Provide the My Oracle Support user name and password, and provide proxy settings if needed. After you download the updates, transfer the update file to a directory on the server where you plan to run the installation.
This section provides information about how to use OUI to install Oracle Grid Infrastructure. It contains the following sections:
Complete the following steps to install Oracle Grid Infrastructure (Oracle Clusterware and Oracle ASM) on your cluster. You can run OUI from a Virtual Network Computing (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. After the installation interview, you can click Details to see the log file.
After you have specified all the information needed for installation, OUI installs the software then runs Oracle Net Configuration Assistant (NETCA), Oracle Private Interconnect Configuration Assistant, and Cluster Verification Utility (CVU). These programs run without user intervention.
If you selected to Oracle ASM as the storage option for the OCR and voting disk files, 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 Oracle Clusterware 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 home:
Grid_home\bin\asmca
When you have verified that your Oracle Grid Infrastructure installation has completed successfully, you can either use Oracle Clusterware to maintain high availability for other applications, or you can install Oracle Database software.
If you intend to install Oracle Database 11g release 2 (11.2) with Oracle RAC, then see Oracle Real Application Clusters Installation Guide for Microsoft Windows x64 (64-Bit). 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:
|
During installation of Oracle 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 name and 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).
There are two steps involved when installing Oracle Grid Infrastructure using the silent method:
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 VIP 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.
To create a cluster configuration file, perform the following steps:
On the installation media, and go to the directory /response
.
Using a text editor, open the response file grid_install.rsp
.
Follow the directions in the sections relevant to the type of installation you are performing, and supply values appropriate for your environment.
See Also: Appendix B, "Installing and Configuring Oracle Grid Infrastructure Using Response Files" for more information about using configuration files |
Complete the following procedure to perform a noninteractive (silent) installation:
Create a cluster configuration file as described in the previous section, "Performing a Silent Installation of Oracle Grid Infrastructure".
Use the following command syntax to run OUI in silent mode:
setup.exe -silent -responseFile path_to_your_response_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 files |
A software-only installation consists of installing Oracle Grid Infrastructure for a cluster on one node. If you use the Install Grid Infrastructure Software Only option during installation, then the Oracle Grid Infrastructure software is installed on the local node. To complete the installation for your cluster, you must perform the additional steps of configuring Oracle Clusterware and Oracle ASM, creating a clone of the local installation, deploying this clone on other nodes, and then adding the other nodes to the cluster.
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:
Configuring the installed software using one of the following methods:
To perform a software-only installation:
Log in to Windows using a member of the Administrators group and run the setup.exe
command from the Oracle Grid Infrastructure 11g Release 2 (11.2) installation media or download directory.
Complete a software-only installation of Oracle Grid Infrastructure for a cluster on the first node, or the local node.
If you are using Oracle Grid Infrastructure release 11.2.0.1 or 11.2.0.2, then 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.
Use OUI as described in steps 1 through 4 to install the Oracle Grid Infrastructure software on every remaining node that you want to include in the cluster, and complete a software-only installation of Oracle Grid Infrastructure on every node
If you installed Oracle Grid Infrastructure release 11.2.0.2 or later, then configure the cluster using the full OUI configuration wizard GUI as described in Section 4.3.2, "Configuring the Software Binaries Using Configuration Wizard Mode of OUI."
If you installed Oracle Grid Infrastructure release 11.2.0.1, then configure the cluster using a response file as described in Appendix B, "Installing and Configuring Oracle Grid Infrastructure Using Response Files."
Starting with Oracle Grid Infrastructure release 11.2.0.2, you can configure the software binaries by starting Oracle Grid Infrastructure configuration wizard in GUI mode.
On one of the nodes, log in as a Local Administrator user, and enter the following command from the crs\config
directory of the Grid home:
C:\..\crs\config> config.bat
The configuration script starts OUI in Configuration Wizard mode. Provide information as needed for configuration. Each page shows the same user interface and performs the same validation checks that OUI normally does. However, instead of running an installation, The configuration wizard mode validates inputs and configures the installation on all cluster nodes.
When you complete inputs, OUI shows you the Summary page, listing all inputs you have provided for the cluster. Verify that the summary has the correct information for your cluster, and click Install to start configuration of the local node.
When configuration of the local node is complete, OUI copies the Oracle Grid Infrastructure configuration file to other cluster member nodes.
Run any scripts, if prompted.
OUI checks the cluster configuration status, and starts other configuration tools as needed.
When you install or copy Oracle Grid Infrastructure software on any node, you can defer configuration for a later time. This section provides the procedure for completing configuration after the software is installed or copied on nodes, using the configuration wizard utility (config.bat
), which is available starting with Oracle Grid Infrastructure release 11.2.0.2.
To configure Oracle Grid Infrastructure for a cluster using a response file:
As the Oracle Grid Infrastructure installation owner (grid
), start OUI in Oracle Grid Infrastructure configuration wizard mode from the Oracle Grid Infrastructure software-only home using the following syntax, where Grid_home
is the Oracle Grid Infrastructure home:
Grid_home\crs\config\config.bat [-debug]
The configuration script starts OUI in Configuration Wizard mode. Each page shows the same user interface and performs the same validation checks that OUI normally does. However, instead of running an installation, the configuration wizard mode validates inputs and configures the installation on all cluster nodes.
When you complete inputs, OUI shows you the Summary page, listing all inputs you have provided for the cluster. Verify that the summary has the correct information for your cluster, and click Install to start configuration of the local node.
When configuration of the local node is complete, OUI copies the Oracle Grid Infrastructure configuration file to other cluster member nodes.
OUI checks the cluster configuration status, and starts other configuration tools as needed.
To configure and activate a software-only Oracle Grid Infrastructure installation for a standalone server, refer to Oracle Database Installation Guide for Microsoft Windows.
This section provides the procedure for completing configuration after the software is installed or copied on nodes, using the configuration wizard utility (config.bat
) in silent (non-response) mode. The configuration wizard utility is available starting with Oracle Grid Infrastructure release 11.2.0.2.
To configure Oracle Grid Infrastructure for a cluster in silent mode using a cluster configuration file:
As the Oracle Grid Infrastructure installation owner (grid
), start OUI in Oracle Grid Infrastructure configuration wizard mode from the Oracle Grid Infrastructure software-only home using the following syntax, where Grid_home
is the Oracle Grid Infrastructure home, and filename
is the response file name, as shown in the following example:
C:\> cd app\11.2.0\grid\crs\config C:\> config.bat -responseFile C:\app\11.2.0\grid\response\grid_install.rsp
The wizard validates the cluster configuration file and proceeds with the configuration. If any of the inputs in the cluster configuration file are found to be invalid, then the Configuration Wizard displays an error and exits. Run the configToolAllCommands
scripts as prompted.
When configuration of the local node is complete, OUI copies the Oracle Grid Infrastructure configuration file to other cluster member nodes.
OUI checks the cluster configuration status, and starts other configuration tools as needed.
After installation, log in as 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
Example 4-1 Checking the Status of Oracle Clusterware
To check the status of the Oracle Clusterware components on each node of your cluster, run the following command:
C:\..\bin\> crsctl check cluster -all
The output for this command is similar to the following:
************************************************************************* 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 software is operational:
srvctl status asm
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.
Example 4-2 Checking the Status of Oracle ASM After Installing Oracle Grid Infrastructure
To verify that your Oracle ASM installation is operational, run the following command, replacing C:\app\11.2.0\grid
with the location of your Grid home. The text below the command is an example of the output returned by the command.
C:\app\11.2.0\grid\BIN> srvctl status asm ASM is running on node node1 ASM is running on node node2
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 RAC or Oracle Database installed, then you cannot use the srvctl program in the database home (Oracle home) to manage Oracle ASM or Oracle Net Services. |
Oracle Grid Infrastructure provides required resources for various Oracle products and components. Some of those products and components are optional, so you can install and enable them after installing Oracle Grid Infrastructure. To simplify postinstallation additions, Oracle Grid Infrastructure preconfigures and registers all required resources for all products available for these products and components, but only activates them when you choose to add them. As a result, some components may be listed as OFFLINE after the installation of Oracle Grid Infrastructure.
Resources listed as TARGET:OFFLINE and STATE:OFFLINE do not need to be monitored. They represent components that are registered, but not enabled, so they do not use any system resources. If an Oracle product or component is installed on the system, and it requires a particular resource to be online, then the software will prompt you to activate the required offline resource.
This appendix describes how to install and configure Oracle Grid Infrastructure software using response files. It includes information about the following topics:
When you start the installer, you can use a response file to automate the installation and configuration of Oracle software, either fully or partially. The installer uses the values contained in the response file to provide answers to some or all installation prompts.
Typically, the installer runs in interactive mode, which means that it prompts you to provide information in graphical user interface (GUI) screens. When you use response files to provide this information, you run the installer from a command prompt using either of the following modes:
If you include responses for all of the prompts in the response file and specify the -silent
option when starting the installer, then it runs in silent mode. During a silent mode installation, the installer does not display any screens. Instead, it displays progress information in the terminal that you used to start it.
If you include responses for some or all of the prompts in the response file and omit the -silent
option, then the installer runs in response file mode. During a response file mode installation, the installer displays all the screens, screens for which you specify information in the response file, and also screens for which you did not specify the required information in the response file.
You define the settings for a silent or response file installation by entering values for the variables listed in the response file. For example, to specify the Oracle home name, supply the appropriate value for the ORACLE_HOME
variable:
ORACLE_HOME="OraCrs11g_home1"
Another way of specifying the response file variable settings is to pass them as command line arguments when you run the installer. For example:
-silent "ORACLE_HOME=OraCrs11g_home1" ...
This method is particularly useful if you do not want to embed sensitive information, such as passwords, in the response file. For example:
-silent "s_dlgRBOPassword=binks342" ...
Ensure that you enclose the variable and its setting in double-quotes.
See Also: Oracle Universal Installer and OPatch User's Guide for Windows and UNIX for more information about response files |
The following table provides use cases for running the installer in silent mode or response file mode.
The following are the general steps to install and configure Oracle products using the installer in silent or response file mode:
Note: You must complete all required preinstallation tasks on a system before running the installer in silent or response file mode. |
Prepare a response file.
Run the installer in silent or response file mode.
If you completed a software-only installation, then perform the steps necessary to configure the Oracle product.
These steps are described in the following sections.
This section describes the following methods to prepare a response file for use during silent mode or response file mode installations:
Oracle provides response file templates for each product and installation type, and for each configuration tool. For Oracle Grid Infrastructure, the response file is located in the staging_dir
\clusterware\response
directory on the installation media and in the Grid_home
\inventory\response
directory after installation.
Table B-1 lists the response files provided with this software:
Table B-1 Response files for Oracle Grid Infrastructure
Response File | Description |
---|---|
Silent installation of Oracle Grid Infrastructure installations |
To copy and modify a response file:
Copy the response file from the response file directory to a directory on your system.
Open the response file in a text editor.
Remember that you can specify sensitive information, such as passwords, at the command line rather than within the response file. "About Response Files" explains this method.
See Also: Oracle Universal Installer and OPatch User's Guide for Windows and UNIX for detailed information on creating response files |
Follow the instructions in the file to edit it.
Note: The installer or configuration assistant fails if you do not correctly configure the response file. |
Secure the response file.
Note: A fully specified response file for an Oracle Grid Infrastructure installation can contain the passwords for Oracle Automatic Storage Management (Oracle ASM) administrative accounts and for a user who is a member of the ORA_DBA group and the Administrators group. Ensure that only the Oracle software owner user can view or modify response files or consider deleting the modified response file after the installation succeeds. |
You can use the installer in interactive mode to record a response file, which you can edit and then use to complete silent mode or response file mode installations. This method is useful for customized or software-only installations. If you use record mode during a response file mode installation, then the installer records the variable values that were specified in the original source response file into the new response file.
Starting with Oracle Database 11g release 2 (11.2), you can save all the installation steps into a response file during installation by clicking Save Response File on the Summary page. You can use the generated response file for a silent installation later.
When you record the response file, you can either complete the installation, or you can exit from the installer on the Summary page, before it starts to copy the software to the server.
Note: Oracle Universal Installer (OUI) does not record passwords in the response file. |
To record a response file:
Complete preinstallation tasks as for a normal installation.
When you run the installer to record a response file, it checks the system to verify that it meets the requirements to install the software. For this reason, Oracle recommends that you complete all of the required preinstallation tasks and record the response file while completing an installation.
Log in as a user that is a member of the local Administrators group. Ensure that this user (the Oracle Grid Infrastructure software owner) has permissions to create or write to the Grid home path that you specify during installation.
Start the installer. On each installation screen, specify the required information.
When the installer displays the Summary screen, perform the following steps:
Click Save Response File. In the pop-up window, specify a file name and location to save the values for the response file, then click Save.
Click Finish to continue with the installation.
Click Cancel if you do not want to continue with the installation. The installation will stop, but the settings you have entered will be recorded in the response file.
Before you use the saved response file on another system, edit the file and make any required changes.
Use the instructions in the file as a guide when editing it.
To use a response file during installation, you start OUI from the command line, specifying the response file you created. The OUI executable, setup.exe
, provides several options. For information about the full set of these options, run the setup.exe
command with the -help
option, for example:
C:\..\bin> setup.exe -help
The help information appears in your session window after a short period of time.
To run the installer using a response file:
Complete the preinstallation tasks as for any installation
Log in as an Administrator user.
To start the installer in silent or response file mode, enter a command similar to the following:
C:\> directory_path\setup.exe [-silent] [-noconfig] \ -responseFile responsefilename
Note: Do not specify a relative path to the response file. If you specify a relative path, then the installer fails. |
In this example:
directory_path
is the path of the DVD or the path of the directory on the hard drive where you have copied the installation software.
-noconfig
suppresses running the configuration assistants during installation, and a software-only installation is performed instead.
responsefilename
is the full path and file name of the installation response file that you configured.
If you use record mode during a response file mode installation, then the installer records the variable values that were specified in the original source response file into the new response file.
You can run Net Configuration Assistant (NETCA) in silent mode to configure and start an Oracle Net listener on the system, configure naming methods, and configure Oracle Net service names. To run NETCA in silent mode, you must copy and edit a response file template. Oracle provides a response file template named netca.rsp
in the database
\inventory\response
directory in the Oracle home directory after installation or in the database\response
directory on the installation media.
To run NETCA using a response file:
Copy the netca.rsp
response file template from the response file directory to a directory on your system.
If you have copied the software to a hard drive, then you can edit the file in the response
directory.
Open the response file in a text editor.
Follow the instructions in the file to edit it.
Note: NETCA fails if you do not correctly configure the response file. |
Log in as an Administrator user and set the ORACLE_HOME
environment variable to specify the correct Oracle home directory.
Enter a command similar to the following to run NETCA in silent mode:
C:\> Oracle_home\bin\netca -silent -responsefile X:\local_dir\netca.rsp
In this command:
The -silent
option runs NETCA in silent mode.
X:\local_dir
is the full path of the directory where you copied the netca.rsp
response file template, where X represents the drive on which the file is located, and local_dir the path on that drive.
Use the following sections to create and run a response file configuration after installing Oracle software.
When you run a silent or response file installation, you provide information about your servers in a response file that you otherwise provide manually using a graphical user interface. However, the response file does not contain passwords for user accounts that configuration assistants require after software installation is complete. The configuration assistants are started with a script called configToolAllCommands
. You can run this script in response file mode by creating and using a password response file. The script uses the passwords to run the configuration tools in succession to complete configuration.
If you keep the password file to use for clone installations, then Oracle strongly recommends that you store it in a secure location. In addition, if you have to stop an installation to fix an error, then you can run the configuration assistants using configToolAllCommands
and a password response file.
The configToolAllCommands
password response file consists of the following syntax options:
internal_component_name is the name of the component that the configuration assistant configures
variable_name is the name of the configuration file variable
value is the desired value to use for configuration.
The command syntax is as follows:
internal_component_name|variable_name=value
For example:
oracle.assistants.asm|S_ASMPASSWORD=myPassWord
Oracle strongly recommends that you maintain security with a password response file.
To run configuration assistants with the configToolAllCommands
script:
Create a response file using the formatfilename
.properties
for the file name.
Open the file with a text editor, and cut and paste the password template, modifying as needed.
Example B-1 Password response file for Oracle Grid Infrastructure Installation
Oracle Grid Infrastructure requires passwords for Oracle Automatic Storage Management Configuration Assistant (ASMCA), and for Intelligent Platform Management Interface Configuration Assistant (IPMICA) if you have a baseboard management controller (BMC) card and you want to enable this feature. Provide the following response file:
oracle.assistants.asm|S_ASMPASSWORD=password oracle.assistants.asm|S_ASMMONITORPASSWORD=password oracle.crs|S_BMCPASSWORD=password
If you do not have a BMC card, or you do not want to enable Intelligent Platform Management Interface (IPMI), then leave the S_BMCPASSWORD
input field blank.
Change directory to Oracle_home
\cfgtoollogs
, and run the configuration script using the following syntax:
configToolAllCommands RESPONSE_FILE=\path\filename.properties
For example:
C:\..\cfgtoollogs> configToolAllCommands RESPONSE_FILE=C:\users\oracle \grid\cfgrsp.properties
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:
There are 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 more advanced 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 (Oracle ASM) 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 Oracle Grid Infrastructure and Oracle RAC" for information about how to complete these tasks |
This section provides a summary of the following pre-installation tasks:
Windows should be optimized for Memory Usage of Programs not System Caching. 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, click the Advanced tab and the settings are displayed at the bottom of the window.
The minimum required RAM is 4 gigabyte (GB) for Oracle Grid Infrastructure for a Cluster and Oracle RAC. The minimum required virtual memory space is 8 GB. Oracle recommends that you set the paging file size to at least one and a half times the amount of RAM for systems with 4 to 32 GB of RAM. For systems with greater than 32 GB of RAM, Oracle recommends that you use a paging file of size 32 GB. If the swap space and the Grid home are on the same file system, then add together their respective requirements for the total minimum space required.
The minimum processor speed is 1 gigahertz (GHz) for Windows Server 2003, Windows Server 2003 R2, and Windows Server 2008. The minimum processor speed is 1.4 GHz for Windows Server 2008 R2.
From the Start menu, select Run... In the Run window, type in Diskmgmt.msc to open the Disk Management graphical user interface (GUI).
The Disk Management GUI displays the available space on the available 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 the Oracle Clusterware files.
If you plan to install the Oracle Clusterware files on Oracle ASM, then to ensure high availability of OCR or voting disk 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.
Starting with Oracle Grid Infrastructure release 11.2.0.3, the minimum disk space the Oracle Grid Infrastructure for a Cluster home (Grid home) required for installation is 5 GB. This includes space for includes space for Oracle Clusterware, Oracle ASM, and Oracle ACFS files and log files, and the Cluster Health Monitor repository.
For Oracle Grid Infrastructure release 11.2.0.2 or 11.2.0.1, ensure you have at least 3 GB of space for the Oracle Grid Infrastructure for a Cluster home (Grid home). This includes Oracle Clusterware and Oracle ASM files and log files.
If the temp space and the Grid home are on the same file system, then add together their respective requirements for the total minimum space required for that file system.
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 of the disk, or delete unnecessary files in the 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), which is used to connect to databases within the cluster irrespective of which nodes the database instances run 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, SCAN contains 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:
NE-sa89-scan
If you require a SCAN that is longer than 15 characters, then the cluster name defaults to the first 15 characters of the SCAN. See Section 1.2.2.2, "IP Address Requirements" for information about the SCAN address requirements.
Before starting the installation, you must have at least two network interface cards (NICs) configured on each node: One for the private internet protocol (IP) addresses and one for the public IP addresses.
Note: Oracle recommends that you use a static host name for all server node public host names. |
The public and virtual IP addresses must be static addresses, configured before installation, and the virtual IP (VIP) addresses for each node must not currently be in use. Public and virtual IP addresses must be on the same subnet. Oracle Clusterware manages private IP addresses in the private subnet on network interfaces you identify as private during the installation interview.
The cluster must have the following addresses configured:
A public IP address for each node, with the following characteristics:
Static IP address
Configured before installation for each node, and resolvable to that node before installation
On the same subnet as all other public IP addresses, VIP addresses, and SCAN addresses
A VIP address for each node, with the following characteristics:
Static IP address
Configured before installation for each node, but not currently in use
On the same subnet as all other public IP addresses, VIP addresses, and SCAN addresses
A single client access name (SCAN) for the cluster, with the following characteristics:
Three static IP addresses configured on the domain name server (DNS) before installation so that the three IP addresses are associated with the name provided as the SCAN, and all three addresses are returned in random order by the DNS to the requestor
Configured before installation in the DNS to resolve to addresses that are not currently in use
Given a name that does not begin with a numeral and conforms with the RFC 952 standard, which allows alphanumeric characters and hyphens ("-"), but does not allow underscores ("_").
On the same subnet as all other public IP addresses, VIP addresses, and SCAN addresses
A private IP address for each node, with the following characteristics:
Static IP address
Configured before installation, but on a separate, private network, with its own subnet. The IP address should not be resolvable except by other cluster member nodes.
The SCAN is a name that is 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 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: In a Typical installation, the SCAN you provide is also the name of the cluster, so the SCAN name must meet the requirements for a cluster name. In an Advanced installation, the SCAN and cluster name are entered in separate fields during installation, so cluster name requirements do not apply to the SCAN name. |
You can use the nslookup
command to confirm that the DNS is correctly associating the SCAN with the addresses. For example:
C:\> nslookup mycluster-scan Server: dns.example.com Address: 192.0.2.001 Name: mycluster-scan.example.com Address: 192.0.2.201 Name: mycluster-scan.example.com Address: 192.0.2.202 Name: mycluster-scan.example.com Address: 192.0.2.203
After installation, when a client sends a request to the cluster, the Oracle Clusterware SCAN listeners redirect client requests to servers in the cluster.
Note: Oracle strongly recommends that you do not configure SCAN VIP addresses in thehosts file. Use DNS resolution for SCAN VIPs. If you use the hosts file to resolve SCANs, then you will only be able to resolve to one IP address and you will have only one SCAN address.
Configuring SCANs in a DNS or a |
See Also: Section C.1.3, "Understanding Network Addresses," for more information about network addresses. |
During installation, you are asked to identify the planned use for each network adapter (or network interface) that Oracle Universal Installer (OUI) detects on your cluster node. You must identify each network adapter as a public or private adapter, or as "do not use." You must use the same private adapters for both Oracle Clusterware and Oracle RAC. For network adapters that you plan to use for other purposes–for example, an adapter dedicated to a network file system–you must identify those network adapters as "do not use" adapters so that Oracle Clusterware ignores them.
If you require high availability or load balancing for public adapters, then use a third party solution. Typically, bonding, trunking or similar technologies can be used for this purpose.
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 must 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 the following registry entry to the Parameters subkey:
Name: DisableDHCPMediaSense Data type: REG_DWORD (Boolean) Value: 1
Exit the Registry Editor and 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.
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
, if the same names are used for the same class of network adapters on each node in the network.
IPv6 is not supported with Oracle Grid Infrastructure. Before installing the Oracle software, disable IPv6 by modifying the registry on all cluster nodes using the following steps:
Start the regedit
program. Create a backup of the current registry settings.
In the Registry Editor, go to the HKEY_LOCAL_MACHINE\SYSTEM\
CurrentControlSet\Services\Tcpip6\Parameters
entry.
Double-click the DisabledComponents key to modify its value. If the DisabledComponents key does not exist, then create this key as follows:
Open the Edit menu.
Select New > DWORD (32-bit) Value.
Enter DisabledComponents, then press Enter to create the key.
For the DisabledComponents key, add a DWORD value of 0xffffffff
.
Exit the Registry Editor and restart the computer.
Repeat these steps on each node on which you plan to install Oracle Grid Infrastructure.
These steps disable all IPv6 components except for the IPv6 loopback interface.
During installation, OUI copies the software from the local node to the remote nodes in the cluster. Verify that you have Administrator privileges on the other nodes in the cluster by running the following command on each node, where nodename
is the name of the remote node:
net use \\nodename\C$
Refer to the tables listed in Section 2.8, "Identifying Software Requirements" for details.
You must configure sufficient space in the Windows virtual memory, or paging file. Paging files are used to store information that cannot fit in RAM, the main memory for the computer. Paging files are shared by all processes, and a lack of space in the paging files can prevent processes from allocating memory.
If possible, split the paging file into multiple files on multiple physical devices. This configuration encourages parallel access to virtual memory, and improves the software performance. See Section 1.2.1.1, "Memory Requirements" for information on configuring the Windows paging file.
To install the Oracle software, you must use an account with Administrator privileges. For more information, refer to the section Section 2.13, "Configuring User Accounts".
Note: If you are performing the installation remotely, refer to Section 2.3, "Logging In To a Remote Windows Server" |
OUI uses several directories during installation of Oracle Grid Infrastructure:
To install properly across all nodes, OUI uses 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 %WINDIR%\temp
and %WINDIR%\tmp
, for example, C:\Windows\temp
or C:\Windows\tmp
for all nodes, if Windows is installed on the C drive.
The directory that Oracle Grid Infrastructure is installed in is referred to as the Grid home. When installing Oracle Grid Infrastructure, you must determine the location of the Grid home. Oracle ASM is also installed in this home directory.
If you plan to install Oracle RAC, you must choose a different directory in which to install the Oracle Database software. The location of the Oracle RAC installation is referred to as the Oracle home.
During installation, you are prompted to specify an Oracle base location, which is owned by the user performing the installation. You can choose a location with an existing Oracle home, or choose another directory location that does not have the structure for an Oracle base directory.
If you install Oracle Database 11g release 2 (11.2) on a computer with no other Oracle software installed, OUI creates an Oracle base directory for you. If Oracle software is already installed, then one or more Oracle base directories already exist. In the latter case, OUI offers you a choice of Oracle base directories to use during installation.
In a default Windows installation, the Oracle base directory appears as follows, where X
represents a disk drive and username
is the name of the currently logged in user:
X:\app\username
Using the Oracle base directory path helps to facilitate the organization of Oracle installations, and helps to ensure that installations of multiple databases maintain an Optimal Flexible Architecture (OFA) configuration.
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
. This directory is created automatically the first time you install Oracle software on a Windows server.
You must have space available on Oracle ASM for Oracle Clusterware files (voting disks and OCRs), and for Oracle Database files, if you install standalone or Oracle RAC databases. Creating Oracle Clusterware files on raw devices is no longer supported for new installations. You can also use Oracle Cluster File System for Windows (OCFS for Windows) for shared storage.
The following topics outline the procedures for preparing disk partitions for use with either Oracle Cluster File System for Windows (OCFS for Windows) or Oracle ASM.
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 have 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 a redundant array of inexpensive disks (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 an existing node in 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 MBR partition style and create an extended partition. Right click inside an unallocated part of a disk and select Create Extended Partition. Specify a size for the partition that is at least 520 megabyte (MB) to store both the OCR and voting disk, or 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 this steps to create enough logical partitions to store all the required files.
For Windows Server 2008 and Windows Server 2008 R2 systems, see Section 3.7, "Configuring Storage for Oracle Database Files on OCFS for Windows" for instructions on creating disk partitions using the DISKPART utility.
On each node in the cluster, ensure that the partitions are visible and that none of the disk partitions created for shared storage 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 stamp the disk partitions by using either asmtoolg
(GUI version) or using asmtool
(command-line version).
Note: On Windows Server 2008 and Windows Server 2008 R2, if user account control (UAC) is enabled, then runningasmtoolg or asmtool utility requires administrator-level permissions. |
This section provides an overview of the installation process for Oracle Grid Infrastructure for a Cluster. For more information, review Section 4.2, "Installing Oracle Grid Infrastructure".
Start OUI from the root level of the installation media. For example, if the installation media is mounted on D: drive, then perform the following at the command prompt:
C:\> D: 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, verify Oracle Clusterware and Oracle ASM are started and functioning correctly.
Oracle Grid Infrastructure Installation Guide for Microsoft Windows x64 (64-Bit) explains how to configure a server in preparation for installing and configuring an Oracle Grid Infrastructure installation (Oracle Clusterware and Oracle Automatic Storage Management). It also explains how to configure a server and storage in preparation for an Oracle Real Application Clusters (Oracle RAC) installation.
Oracle Grid Infrastructure Installation Guide for Microsoft Windows x64 (64-Bit) provides configuration information for network and system administrators, and database installation information for database administrators (DBAs) who install and configure Oracle Clusterware and Oracle Automatic Storage Management in an Oracle Grid Infrastructure for a cluster installation.
For customers with specialized system roles who intend to install Oracle RAC, this book is intended to be used by system administrators, network administrators, or storage administrators to configure a system in preparation for an Oracle Grid Infrastructure for a cluster installation, and complete all configuration tasks that require Administrator user privileges. When the Oracle Grid Infrastructure installation and configuration is successfully completed, a system administrator should only provide configuration information and grant access to the database administrator to run scripts that require Administrator user privileges during an Oracle RAC installation.
This guide assumes that you are familiar with Oracle Database concepts. For additional information, refer to books in the Related Documents list.
For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc
.
Access to Oracle Support
Oracle customers have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info
or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs
if you are hearing impaired.
For more information, refer to the following Oracle resources.
Oracle Clusterware and Oracle Real Application Clusters Documentation
This installation guide reviews steps required to complete an Oracle Clusterware and Oracle Automatic Storage Management installation, and to perform preinstallation steps for Oracle RAC.
If you intend to install Oracle Database or Oracle RAC, then complete the preinstallation tasks as described in this installation guide. Next, complete the Oracle Grid Infrastructure installation, and review the Oracle Database and Oracle RAC installation guides for additional information. You can install either Oracle databases for a standalone server on an Oracle Grid Infrastructure installation, or install an Oracle RAC database. To install an Oracle Restart deployment of Oracle Grid Infrastructure, see Oracle Database Installation Guide for Microsoft Windows x64 (64-Bit).
Most Oracle error message documentation is only available in HTML format. If you only have access to the Oracle Documentation media, then browse the error messages by range. When you find the correct range of error messages, use your browser's Find feature to locate a specific message. When connected to the Internet, you can search for a specific error message using the error message search feature of the Oracle online documentation.
Installation Guides
Oracle Diagnostics Pack Installation Guide
Oracle Database Installation Guide for Microsoft Windows x64 (64-Bit)
Oracle Real Application Clusters Installation Guide for Microsoft Windows x64 (64-Bit)
Operating System-Specific Administrative Guides
Oracle Database Platform Guide for Microsoft Windows
Oracle Clusterware and Oracle Automatic Storage Management Administrative Guides
Oracle Clusterware Administration and Deployment Guide
Oracle Automatic Storage Management Administrator's Guide
Oracle Real Application Clusters Administrative Guides
Oracle Real Application Clusters Administration and Deployment Guide
Oracle Database 2 Day + Real Application Clusters Guide
Generic Documentation
Getting Started with the Oracle Diagnostics Pack
Oracle Database 2 Day DBA
Oracle Database Administrator's Guide
Oracle Database Concepts
Oracle Database New Features Guide
Oracle Database Net Services Administrator's Guide
Oracle Database Reference
To download free release notes, installation documentation, white papers, or other collateral, visit the Oracle Technology Network (OTN). You must register online before using OTN; registration is free and can be done at the following web site:
http://www.oracle.com/technetwork/community/join/overview/
If you have a username and password for OTN, then you can go directly to the documentation section of the OTN web site at the following web site:
http://www.oracle.com/technetwork/indexes/documentation/
Oracle error message documentation is available only in HTML. You can browse the error messages by range in the Documentation directory of the installation media. When you find a range, use your browser's Find feature to locate a specific message. When connected to the Internet, you can search for a specific error message using the error message search feature of the Oracle online documentation.
The following text conventions are used in this document:
Convention | Meaning |
---|---|
boldface | Boldface type indicates graphical user interface elements associated with an action, or terms defined in text or the glossary. |
italic | Italic type indicates book titles, emphasis, or placeholder variables for which you supply particular values. |
monospace | Monospace type indicates commands within a paragraph, URLs, code in examples, text that appears on the screen, or text that you enter. |