Skip Headers
Oracle® Grid Infrastructure Installation Guide
11g Release 2 (11.2) for Microsoft Windows

Part Number E10817-01
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
View PDF

5 Oracle Grid Infrastructure Postinstallation Procedures

This chapter describes how to complete the postinstallation tasks after you have installed the Oracle Grid Infrastructure software.

This chapter contains the following topics:

5.1 Required Postinstallation Tasks

You must perform the following tasks after completing your installation:

Note:

In prior releases, backing up the voting disks using the ocopy.exe command was a required postinstallation task. With Oracle Clusterware release 11.2 and later, backing up a voting disk is no longer required.

5.1.1 Download and Install Patch Updates

Refer to the My Oracle Support Web site for required patch updates for your installation.

To download required patch updates:

  1. Use a Web browser to view the My Oracle Support Web site:

    https://support.oracle.com

  2. Log in to My Oracle Support Web site.

    Note:

    If you are not a My Oracle Support registered user, then click Register Here and register.
  3. On the main My Oracle Support page, select Patches & Updates.

  4. On the Patches & Update page, in the click Advanced "Classic" Patch Search.

    If you want to search for patch sets, click the Latest Patchsets link under the heading Oracle Server/Tools.

  5. On the Advanced Search page, click the search icon next to the Product or Product Family field.

  6. In the Search and Select: Product Family field, select Database and Tools in the Search list field, enter Database in the text field, and click Go.

    Click Oracle Database Family in the list of Product Names to select it.

  7. Click the search icon next to the Release field. In the Search and Select: Release window, type 11.2 in the Search field, then click Go. Click Oracle 11.2.0.1.0 in the Release Name column to select it.

  8. Select your platform from the Platform or Language drop-down list (for example, Microsoft Windows Server 2003 R2).

  9. At the bottom of the Advanced Search section, click Go. Any available patch updates appear under the Results heading.

  10. Click the patch number to view the patch description and access the README file for the patch. You can also download the patch from this page.

  11. Click View README and read the page that appears. The README page contains information about the patch and how to apply the patch to your installation.

    Click Patch Details to return to the previous page.

  12. Click Download, and save the patch file on your system.

  13. Use the unzip utility provided with your Oracle software to uncompress the Oracle patch updates that you download from My Oracle Support. The unzip utility is located in the Grid_home\BIN directory.

  14. Refer to Appendix D, "How to Upgrade to Oracle Grid Infrastructure 11g Release 2" for information about how to stop database processes in preparation for installing patches.

5.1.2 Configure Exceptions for the Windows Firewall

If the Windows Firewall feature is enabled on one or more of the nodes in your cluster, then virtually all TCP network ports are blocked to incoming connections. As a result, any Oracle product that listens for incoming connections on a TCP port will not receive any of those connection requests and the clients making those connections will report errors.

You must configure exceptions for the Windows Firewall if your system meets all of the following conditions:

  • Oracle server-side components are installed on a computer running a supported version of Microsoft Windows. The list of components includes the Oracle Database, Oracle grid infrastructure, Oracle RAC, network listeners, or any Web servers or services.

  • The Windows machine in question accepts connections from other machines over the network. If no other machines will be connecting to the Windows machine to access the Oracle software, then no post-installation configuration steps are required and the Oracle software will function as expected.

  • The Windows machine in question is configured to run the Windows Firewall. If the Windows Firewall is not enabled, then no post-installation configuration steps are required.

If all of the above conditions are met, then the Windows Firewall must be configured to allow successful incoming connections to the Oracle software. To enable Oracle software to accept connection requests, Windows Firewall needs to be configured by either opening up specific static TCP ports in the firewall or by creating exceptions for specific executables so they can receive connection requests on any ports they choose. This firewall configuration can be done by one of the following methods:

  • Start the Windows Firewall application, select the Exceptions tab and then click either Add Program or Add Port to create exceptions for the Oracle software.

  • From the command prompt, use the netsh firewall add... command.

  • When Windows notifies you that a foreground application is attempting to listen on a port, and gives you the opportunity to create an exception for that executable. If you choose the create the exception in this way, the effect is the same as creating an exception for the executable either via Control Panel or from the command line.

The following sections list the Oracle Database 11g release 2 executables that listen on TCP ports on Windows, along with a brief description of the executable. It is recommended that these executables (if in use and accepting connections from a remote, client machine) be added to the exceptions list for the Windows Firewall to ensure correct operation. In addition, if multiple Oracle homes are in use, firewall exceptions may need to be created for the same executable, for example, oracle.exe, multiple times, once for each Oracle home from which that executable loads.

5.1.2.1 Firewall Exceptions for Oracle Database

For basic database operation and connectivity from remote clients (SQL*Plus, OCI, ODBC, OLE DB applications, and so on), the following executables need to be added to the Windows Firewall exception list:

  • Oracle_home\bin\oracle.exe - Oracle Database executable

  • Oracle_home\bin\tnslsnr.exe - Oracle Listener

If you use remote monitoring capabilities for your database, the following executables need to be added to the Windows Firewall exception list:

  • Oracle_home\bin\emagent.exe - Oracle Database Control

  • Oracle_home\jdk\bin\java.exe - Java Virtual Machine for Enterprise Manager Database Control

5.1.2.2 Firewall Exceptions for Oracle Database Examples (or the Companion CD)

After installing the Oracle Database Companion CD, the following executables need to be added to the Windows Firewall exception list:

  • Oracle_home\opmn\bin\opmn.exe - Oracle Process Manager

  • Oracle_home\jdk\bin\java.exe - Java Virtual Machine

5.1.2.3 Firewall Exceptions for Oracle Gateways

If your Oracle database interacts with non-Oracle software through a gateway, then you need to add the gateway executable to the Windows Firewall exception list. Table 5-1table lists the gateway executables used to access non-Oracle software.

Table 5-1 Oracle Executables Used to Access Non-Oracle Software

Executable Name Description

omtsreco.exe

Oracle Services for Microsoft Transaction Server

dg4sybs.exe

Oracle Database Gateway for Sybase

dg4tera.exe

Oracle Database Gateway for Teradata

dg4msql.exe

Oracle Database Gateway for SQL Server

dg4db2.exe

Oracle Database Gateway for DRDA

pg4arv.exe

Oracle Database Gateway for APPC

pg4t4ic.exe

Oracle Database Gateway for APPC

dg4mqs.exe

Oracle Database Gateway for WebSphere MQ

dg4mqc.exe

Oracle Database Gateway for WebSphere MQ

dg4odbc.exe

Oracle Database Gateway for ODBC


5.1.2.4 Firewall Exceptions for Oracle Clusterware and Oracle ASM

If you installed the Oracle grid infrastructure software on the nodes in your cluster, then you can enable the Windows Firewall only after adding the following executables and ports to the Firewall exception list. The Firewall Exception list must be updated on each node.

  • Grid_home\bin\gpnpd.exe - Grid Plug and Play daemon

  • Grid_home\bin\oracle.exe - Oracle ASM executable (if using Oracle ASM for storage)

  • Grid_home\bin\racgvip.exe - Virtual Internet Protocol Configuration Assistant

  • Grid_home\bin\evmd.exe - OracleEVMService

  • Grid_home\bin\crsd.exe - OracleCRService

  • Grid_home\bin\ocssd.exe - OracleCSService

  • Grid_home\bin\octssd.exe - Cluster Time Synchronization Service daemon

  • Grid_home\bin\mDNSResponder.exe - multicast-DNS Responder Daemon

  • Grid_home\bin\gipcd.exe - Grid IPC daemon

  • Grid_home\bin\gnsd.exe - Grid Naming Service daemon

  • Grid_home\bin\ohasd.exe - OracleOHService

  • Grid_home\bin\TNSLSNR.EXE - SCAN listener and local listener for Oracle RAC database and Oracle ASM

  • Grid_home\opmn\bin\ons.exe - Oracle Notification Service

  • Grid_home\jdk\jre\bin\java.exe - Java Virtual Machine

5.1.2.5 Firewall Exceptions for Oracle RAC Database

For the Oracle RAC database, the executables that require exceptions are:

  • Oracle_home\bin\oracle.exe - Oracle RAC database instance

  • Oracle_home\bin\emagent.exe - Oracle Enterprise Manager agent

  • Oracle_home\jdk\bin\java.exe - For the Oracle Enterprise Manager DB Console

In addition, the following ports should be added to the Windows Firewall exception list:

  • Microsoft file sharing SMB

    • User Datagram Protocol (UDP) ports from 135 through 139

    • Transmission Control Protocol (TCP) ports from 135 through 139

  • Direct-hosted SMB traffic without a network basic input/output system (NetBIOS)

    • port 445 (TCP and UPD)

5.1.2.6 Firewall Exceptions for Oracle Cluster File System for Windows

If you use Oracle Cluster File System (OCFS) for Windows to store the Oracle Clusterware files, or Oracle RAC database files, then you must add the following exceptions to the Windows Firewall:

  • Grid_home\cfs\Ocfsfindvol.exe - Oracle Cluster File System (OCFS) for Windows Volume Service

  • %WINDOWS_HOME%\system32\drivers\Ocfs.sys - System file for Oracle Cluster File System (if using OCFS for Windows for Oracle Clusterware storage)

5.1.2.7 Firewall Exceptions for Other Oracle Products

In additional to all the previously listed exceptions, if you use any of the Oracle software listed in, then you must create an exception for Windows Firewall for the associated executable.

Table 5-2 Other Oracle Software Products Requiring Windows Firewall Exceptions

Oracle Software Product Executable Name

Data Guard Manager

dgmgrl.exe

Oracle Internet Directory LDAP Server

oidldapd.exe

External Procedural Calls

extproc.exe


5.2 Recommended Postinstallation Tasks

Oracle recommends that you complete the following tasks as needed after installing Oracle Grid Infrastructure:

5.2.1 Install Troubleshooting Tool

To address troubleshooting issues, Oracle recommends that you install Instantaneous Problem Detection OS Tool (IPD/OS).

5.2.1.1 Installing Instantaneous Problem Detection OS Tool (IPD/OS)

On Windows systems running Windows Server 2003 with service pack 2 or higher, install the Oracle Instantaneous problem Detection Operating System Tool (IPD/OS).

The IPD/OS tool is designed to detect and analyze operating system and cluster resource-related degradation and failures. The tool can provide better explanations for many issues that occur in clusters where Oracle Clusterware and Oracle RAC are running, such as node evictions. It tracks the operating system resource consumption at each node, process, and device level continuously. It collects and analyzes clusterwide data. In real time mode, when thresholds are reached, an alert is shown to the operator. For root cause analysis, historical data can be replayed to understand what was happening at the time of failure.

You can download the tool at the following URL:

http://www.oracle.com/technology/products/database/clustering/ipd_download_homepage.html

To prevent performance problems, you cannot run the GUI interface for IPD/OS on the Oracle RAC node. You can install the client on any Linux or Windows client that is not a cluster member node. From this client you can view the data.

5.2.2 Optimize Memory Usage for Programs

The Windows operating system should be optimized for Memory Usage of 'Programs' instead of 'System Caching'. To modify the memory optimization settings, perform the following steps:

  1. From the Start Menu, select Control Panel, then System.

  2. In the System Properties window, click the Advanced tab.

  3. In the Performance section, click Settings.

  4. In the Performance Options window, click the Advanced tab.

  5. In the Memory Usage section, make sure Programs is selected.

5.2.3 Create a Fast Recovery Area Disk Group

During installation, if you select Oracle ASM for storage, a single disk group is created. If you plan to add an Oracle Database for a standalone server or an Oracle RAC database, then you should create a separate disk group for the fast recovery area.

5.2.3.1 About the Fast Recovery Area and the Fast Recovery Area Disk Group

The fast recovery area is a unified storage location for all Oracle Database files related to recovery. Database administrators can define the DB_RECOVERY_FILE_DEST parameter to the path for the Fast Recovery Area to enable on-disk backups, and rapid recovery of data. Enabling rapid backups for recent data can reduce requests to system administrators to retrieve backup tapes for recovery operations.

When you enable the fast recovery area in the init.ora file, all RMAN backups, archive logs, control file automatic backups, and database copies are written to the fast recovery area. RMAN automatically manages files in the fast recovery area by deleting obsolete backups and archive files that are no longer required for recovery.

To use a flash recovery area in Oracle RAC, you must place it on an Oracle ASM disk group, a cluster file system, or on a shared directory that is configured through Direct NFS for each Oracle RAC instance. In other words, the flash recovery area must be shared among all of the instances of an Oracle RAC database.Oracle recommends that you create a fast recovery area disk group. Oracle Clusterware files and Oracle Database files can be placed on the same disk group as fast recovery area files. However, Oracle recommends that you create a separate fast recovery area disk group to reduce storage device contention.

The fast recovery area is enabled by setting DB_RECOVERY_FILE_DEST. The parameter DB_RECOVERY_FILE_DEST to the same value on all instances. The size of the fast recovery area is set with DB_RECOVERY_FILE_DEST. As a general rule, the larger the fast recovery area, the more useful it becomes. For ease of use, Oracle recommends that you create a fast recovery area disk group on storage devices that can contain at least three days of recovery information. Ideally, the fast recovery area should be large enough to hold a copy of all of your data files and control files, the online redo logs, and the archived redo log files needed to recover your database using the data file backups kept under your retention policy.

Multiple databases can use the same fast recovery area. For example, assume you have created one fast recovery area disk group on disks with 150 GB of storage, shared by three different databases. You can set the size of the fast recovery area for each database depending on the importance of each database. For example, if database1 is your least important database, database2 is of greater importance and database3 is of greatest importance, then you can set different DB_RECOVERY_FILE_DEST_SIZE settings for each database to meet your retention target for each database: 30 GB for database1, 50GB for database2, and 70GB for database3.

5.2.3.2 Creating the Fast Recovery Area Disk Group

To create a fast recovery area disk group:

  1. Navigate to the Grid home bin directory, and start Oracle ASM Configuration Assistant (ASMCA). For example:

    C:\> cd app\11.2.0\grid\bin
    C:\> asmca
    
  2. ASMCA opens at the Disk Groups tab. Click Create to create a new disk group

  3. The Create Disk Groups window opens.

    In the Disk Group Name field, enter a descriptive name for the fast recovery area group. For example: FRA.

    In the Redundancy section, select the level of redundancy you want to use.

    In the Select Member Disks field, select eligible disks to be added to the fast recovery area, and click OK.

  4. The Diskgroup Creation window opens to inform you when disk group creation is complete. Click OK.

  5. Click Exit.

5.3 Using Older Oracle Database Versions with Grid Infrastructure

Review the following sections for information about using older Oracle Database releases with Oracle Clusterware 11g release 2 (11.2) installations:

5.3.1 General Restrictions for Using Older Oracle Database Versions

You can use Oracle9i Database release 2, Oracle Database 10g releases 1 and 2, and Oracle Database 11g release 1 with Oracle Clusterware 11g release 2 (11.2).

If you upgrade an existing version of Oracle Clusterware, then the required configuration of existing databases is completed automatically. However, if you complete a new installation of Oracle Grid Infrastructure for a cluster, and then want to install Oracle Database 11g release 1 or any prior release, then you must complete additional manual configuration tasks.

5.3.2 Pinning Cluster Nodes for Oracle Database Release 10.x or 11.x

When Oracle Database version 10.x or 11.x is installed on a new Oracle Grid Infrastructure for a cluster configuration, it is configured for dynamic cluster configuration, in which some or all IP addresses are provisionally assigned, and other cluster identification information is dynamic. This configuration is incompatible with older database releases, which require fixed addresses and configurations.

You can change the nodes where you want to run the older database to create a persistent configuration. Creating a persistent configuration for a node is called pinning a node.

To pin a node in preparation for installing an older Oracle Database version, use CRS_home\bin\crsctl with the following command syntax, where nodes is a space-delimited list of one or more nodes in the cluster whose configuration you want to pin:

crsctl pin css -n nodes

For example, to pin nodes node3 and node4, log in as an Administrator user and enter the following command:

C:\> crsctl pin css -n node3 node4

To determine if a node is in a pinned or unpinned state, use CRS_home\bin\olsnodes with the following syntax:

olsnodes -t -n 

For example, to list all pinned nodes, use the following command:

C:\> app\11.2.0\grid\bin\olsnodes -t -n
node1 1       Pinned
node2 2       Pinned
node3 3       Pinned
node4 4       Pinned

To list the state of a particular node use the -n option, as shown in the following example:

C:\> app\11.2.0\grid\bin\olsnodes -t -n node3
node3 3       Pinned

See Also:

Oracle Clusterware Administration and Deployment Guide for more information about pinning and unpinning nodes

5.3.3 Enabling the Global Services Daemon (GSD) for Oracle Database Release 9.2

To install an Oracle Database version 9.2 on a cluster running Oracle Clusterware 11g (version 11.1 or higher), perform the following additional configuration steps to prevent permission errors:

  1. Create the OracleCRSToken_username for the Oracle9i software owner on each node in the cluster. After the service is created, change the ownership for the GSD resource to the Oracle9i software owner.

    Run the following commands on each node using the specified syntax, where Grid_home is the Oracle Grid infrastructure home, 92_user_domain is the domain of the Oracle9i software owner, 92_username is the user name of the Oracle9i software owner, and nodename is the name of the node on which the service is being configured:

    Grid_home\bin\crsctl add crs administrator 92_domain/92_username
    Grid_home\bin\crsctl setperm resource ora.nodename.gsd -o 92_username
    

    For example, if the Oracle Clusterware home is C:\app\11.2.0\grid, the domain is ORAUSERS, the node name is node1, and the username is ora92, then you would enter the following commands:

    C:\app\11.2.0\grid\bin> crsctl add crs administrator ORAUSERS/ora92
    C:\app\11.2.0\grid\bin> crsctl setperm resource ora.node1.gsd 
     -o ORAUSERS/ora92
    
  2. Enable and start the GSD daemon on all nodes in the cluster.

    On any node in the cluster, run commands using the following syntax, where Grid_home is the Oracle Grid infrastructure home:

    Grid_home\bin\srvctl enable nodeapps -g
    Grid_home\bin\srvctl start nodeapps 
    

    For example, if the Oracle Clusterware home is C:\app\11.2.0\grid, then enter the following commands:

    C:\app\11.2.0\grid\bin> srvctl enable nodeapps -g
    C:\app\11.2.0\grid\bin> srvctl start nodeapps
    

5.3.4 Using the Correct LSNRCTL Commands

To administer Oracle Clusterware and Oracle ASM 11g release 2 local and scan listeners using the lsnrctl command, use the Listener Control utility in the grid infrastructure home (Grid home). Do not attempt to use the lsnrctl commands from Oracle home locations for previous releases, because they cannot be used with the new release.

5.4 Modifying Oracle Clusterware Binaries After Installation

After installation, if you need to modify the software installed in your Grid home, then you must first stop the Oracle Clusterware stack. For example, if you want to apply a one-off patch or modify any of the DLLs used by Oracle Clusterware or Oracle ASM, then you must follow these steps to stop and restart the Oracle Clusterware stack.

Caution:

To put the changes you make to the Oracle grid infrastructure home into effect, you must shut down all executables that run in the Grid home directory and then restart them. In addition, shut down any applications that use Oracle shared libraries or DLL files in the Grid home.

Prepare the Oracle grid infrastructure home for modification using the following procedure:

  1. Log in using a member of the Administrators group and change directory to the path Grid_home\bin, where Grid_home is the path to the Oracle grid infrastructure home.

  2. Shut down the Oracle Clusterware stack using the following command:

    C:\..\bin> crsctl stop crs -f
    
  3. After the Oracle Clusterware stack is completely shut down, perform the updates to the software installed in the Grid home.

  4. Use the following command to restart the Oracle Clusterware stack:

    C:\..\bin> crsctl start crs
    
  5. Repeat steps 1 through 4 on each cluster member node.