This chapter describes how to complete the postinstallation tasks after you have installed the Oracle Grid Infrastructure software.
This chapter contains the following topics:
Note:In prior releases, backing up the voting disks using the
ocopy.execommand was a required postinstallation task. With Oracle Clusterware 11g Release 2 (11.2) and later releases, backing up a voting disk is no longer required.
Note:Browsers require an Adobe Flash plug-in, version 9.0.115 or higher to use My Oracle Support. Check your browser for the correct version of Flash plug-in by going to the Adobe Flash checker page, and installing the latest version of Adobe Flash.
If you do not have Flash installed, then download the latest version of the Flash Player from the Adobe web site:
On a regular basis Oracle provides patch sets that include generic and port specific fixes encountered by customers since the base product was released. Patch sets increment the 4th digit of the version number e.g. 10.2.0.1.0 to 10.2.0.4.0, these patch sets are fully regression tested in the same way that the base release is (i.e. 10.2.0.1.0). Customers are encouraged to apply these fixes.
If a customer encounters a critical problem that requires a fix prior to the next patch set becoming available, they can request that a one off fix is made available on top of the latest patch set. This delivery mechanism is similar to the Microsoft Hot Fixes and is known as an Oracle patch set exception (or interim patch). Unlike Unix platforms these patch set exceptions are delivered in a patch set exception bundle (cumulative patch bundle), which includes all fixes since the current patch set. For example, bug 12393432 is a patch set exception bundle, Patch 12, for Oracle Database release 188.8.131.52 for Microsoft Windows (x64). You should always apply the latest patch bundle available for your release.
The patch set exception bundles also include the fixes for the CPU (Critical Patch Update), DST (Daylight Saving Time), PSU (Patch Set Update) and Recommended Patch Bundles. It is not required to have previous security patches applied before applying the patch set exception bundle. However, you must be on the stated patch set level for a given product home before applying the patch set exception bundle for that release.
To download required patch updates:
Use a web browser to view the My Oracle Support web site:
Log in to My Oracle Support web site.
Note:If you are not a My Oracle Support registered user, then click Register Here to register.
On the main My Oracle Support page, click Patches & Updates.
To search for patch sets, perform the following steps:
Click the Latest Patch sets link on the left side of the page, under the heading Oracle Server/Tools.
The Quick Links page appears in a new browser window or tab.
Click Simple Search.
Set the Search By field to Product or Family. Click the flashlight icon next to the adjacent text field. In the popup window, in the text field next to All Products, type "%Oracle Database%", then click Go.
Select Oracle Database Family from the list, then click Select to return to the Simple Search window.
Choose a value for Patch set release, for example, Oracle 184.108.40.206.0.
Note:The Patch set release is one greater than your current software release. For example, if your current software release is Oracle 10.2.0.3, then the Patch set release would Oracle 10.2.0.4.
For the Patch Type, select Patch set/Minipack.
For the Platform or Language, select Microsoft Windows x64 (64-bit).
Click Go. Continue with Step 6.
To search for patches, perform the following steps:
On the right side of the page, in the Patch Search section, select Product or Family (Advanced Search).
In the Product or Family Search section, select Oracle Database for the Product and Oracle 220.127.116.11.0 (Oracle Database) for the Release. If you have applied any of the bundle patches, then used the modified database version, for example 18.104.22.168.3, instead of the base version number (22.214.171.124.0).
If a search filter for Platform is visible, select Microsoft Windows x64 (64-bit) for the Platform. If this search filter is not visible, either add this search filter, or select Platform from the drop-down list for the last search filter line.
A list of all available patches for the specified Oracle Database release on Microsoft Windows x64 platforms is displayed.
(Optional) To locate patches specific to Oracle RAC or Oracle Grid Infrastructure, click Edit Search. When returned to the Product or Family Search window, add a filter for Patch Target, and set the value to Real Application Clusters.
Note:Because Oracle RAC is an option of the Oracle Database software, patches that apply to Oracle Database also apply to Oracle RAC databases.
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.
Click Read Me to view the patch instructions. The README page is opened in a separate browser window or tab. The README file contains information about the patch, a list of bugs fixed by this patch, and how to apply the patch to your installation.
Close the tab or window to return to the previous page.
Click Download, and save the patch file on your system.
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
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.
If the Windows Firewall feature is enabled on one or more of the nodes in your cluster, then virtually all transmission control protocol (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 Real Application Clusters (Oracle RAC), network listeners, or any web servers or services.
The Windows computer in question accepts connections from other computers over the network. If no other computers connect to the Windows computer to access the Oracle software, then no post-installation configuration steps are required and the Oracle software functions as expected.
The Windows computer 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 must 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 through 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 computer) 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 have to be created for the same executable, for example,
oracle.exe, multiple times, once for each Oracle home from which that executable loads.
For basic database operation and connectivity from remote clients, such as SQL*Plus, Oracle Call Interface (OCI), Open Database Connectivity (ODBC), Object Linking and Embedding database (OLE DB) applications, and so on, the following executables must be added to the Windows Firewall exception list:
\bin\oracle.exe - Oracle Database executable
\bin\tnslsnr.exe - Oracle Listener
If you use remote monitoring capabilities for your database, the following executables must be added to the Windows Firewall exception list:
emagent.exe - Oracle Database Control
\jdk\bin\java.exe - Java Virtual Machine (JVM) for Enterprise Manager Database Control
After installing the Oracle Database Companion CD, the following executables must be added to the Windows Firewall exception list:
\opmn\bin\opmn.exe - Oracle Process Manager
\jdk\bin\java.exe - JVM
If your Oracle database interacts with non-Oracle software through a gateway, then you must add the gateway executable to the Windows Firewall exception list. Table 5-1table lists the gateway executables used to access non-Oracle software.
Oracle Services for Microsoft Transaction Server
Oracle Database Gateway for Sybase
Oracle Database Gateway for Teradata
Oracle Database Gateway for SQL Server
Oracle Database Gateway for Distributed Relational Database Architecture (DRDA)
Oracle Database Gateway for Advanced Program to Program Communication (APPC)
Oracle Database Gateway for APPC
Oracle Database Gateway for WebSphere MQ
Oracle Database Gateway for WebSphere MQ
Oracle Database Gateway for ODBC
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.
\bin\gpnpd.exe - Grid Plug and Play daemon
\bin\oracle.exe - Oracle Automatic Storage Management (Oracle ASM) executable (if using Oracle ASM for storage)
\bin\racgvip.exe - Virtual Internet Protocol Configuration Assistant
\bin\evmd.exe - OracleEVMService
\bin\crsd.exe - OracleCRService
\bin\ocssd.exe - OracleCSService
\bin\octssd.exe - Cluster Time Synchronization Service daemon
\bin\mDNSResponder.exe - multicast-domain name system (DNS) Responder Daemon
\bin\gipcd.exe - Grid inter-process communication (IPC) daemon
\bin\gnsd.exe - Grid Naming Service (GNS) daemon
\bin\ohasd.exe - OracleOHService
\bin\TNSLSNR.EXE - single client access name (SCAN) listener and local listener for Oracle RAC database and Oracle ASM
\opmn\bin\ons.exe - Oracle Notification Service (ONS)
\jdk\jre\bin\java.exe - JVM
\bin\oracle.exe - Oracle RAC database instance
\bin\emagent.exe - Oracle Enterprise Manager agent
\jdk\bin\java.exe - For the Oracle Enterprise Manager Database Console
In addition, the following ports should be added to the Windows Firewall exception list:
Microsoft file sharing system management bus (SMB)
User Datagram Protocol (UDP) ports from 135 through 139
TCP ports from 135 through 139
Direct-hosted SMB traffic without a network basic I/O system (NetBIOS)
port 445 (TCP and UPD)
If you use Oracle Cluster File System for Windows (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:
\cfs\Ocfsfindvol.exe - OCFS for Windows Volume Service
%WINDOWS_HOME%\system32\drivers\Ocfs.sys - System file for OCFS (if using OCFS for Windows for Oracle Clusterware storage)
In addition 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.
To address troubleshooting issues, Oracle recommends that you install Instantaneous Problem Detection OS Tool (IPD/OS). This utility is available on Oracle Technology Network (OTN) for Oracle Grid Infrastructure 126.96.36.199 installations.
Note:With the Oracle Grid Infrastructure 11g Release 2 (11.2) release, the IPD/OS utility was updated and renamed to Cluster Health Monitor (CHM). CHM is not available for Windows platforms until Oracle Grid Infrastructure release 188.8.131.52, and IPD/OS is not compatible with the first patch set release of Oracle Grid Infrastructure 11g Release 2 (184.108.40.206).
On Windows systems running Windows Server 2003 with service pack 2 or higher, you can install IPD/OS. IPD/OS supports both x86 and x64 installations.
Note:If you already have IPD/OS installed on your cluster, then you will have to remove the current version before installing the new version.
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 IPD/OS by clicking the link titled Cluster Health Monitor - Download at the following URL:
To prevent performance problems, you cannot run the graphical user interface (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.
See Also:The README file for IPD/OS for more information about installing the IPD/OS tool and client
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:
From the Start Menu, select Control Panel, then System.
In the System Properties window, click the Advanced tab.
In the Performance section, click Settings.
In the Performance Options window, click the Advanced tab.
In the Memory Usage section, make sure Programs is selected.
During installation of Oracle Grid Infrastructure, if you select Oracle ASM for storage, a single disk group is created to store the Oracle Clusterware files. If you plan to create a single-instance database, an Oracle RAC database, or an Oracle RAC One Node database, then this disk group can also be used to store the data files for the database. However, you should create a separate disk group for the fast recovery area.
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 database initialization parameter 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 fast 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 network file system (NFS) for each Oracle RAC instance. In other words, the fast recovery area must be shared among all of the instances of an Oracle RAC database. 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 the parameter
DB_RECOVERY_FILE_DEST to the same value on all instances. The size of the fast recovery area is set with the parameter
DB_RECOVERY_FILE_DEST_SIZE. 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 gigabyte (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, 50 GB for
database2, and 70 GB for
To create an Oracle ASM disk group for the fast recovery area:
C:\> cd app\11.2.0\grid\bin C:\> asmca
ASMCA opens at the Disk Groups tab. Click Create to create a new disk group
The Create Disk Groups window opens.
In the Disk Group Name field, enter a descriptive name for the fast recovery area disk 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.
The Diskgroup Creation window opens to inform you when disk group creation is complete. Click OK.
Review the following sections for information about using earlier Oracle Database releases with Oracle Grid Infrastructure 11g Release 2 (11.2) installations:
You can use Oracle Database release 10.2 and release 11.1 with Oracle Clusterware and Oracle ASM release 11.2. If you upgrade an existing version of Oracle Clusterware and Oracle ASM to Oracle Grid Infrastructure 11g Release 2 (which includes Oracle Clusterware and Oracle ASM), and you also plan to upgrade your Oracle RAC database to Oracle Database 11g Release 2, then the required configuration of the existing databases is completed automatically when you complete the Oracle RAC upgrade, and this section does not concern you.
Note:Refer to Oracle Automatic Storage Management Administrator's Guide for details on configuring disk group compatibility for databases using Oracle Database versions 11.1 or earlier with Oracle Grid Infrastructure 11.2.
However, if you upgrade to Oracle Grid Infrastructure 11g Release 2, and you have existing Oracle RAC installations that you do not plan to upgrade, or if you install earlier versions of Oracle RAC (10.2 or 11.1) on a cluster running Oracle Grid Infrastructure 11g Release 2, then you must complete additional configuration tasks or apply patches, or both, before the earlier database versions will work correctly with Oracle Grid Infrastructure.
Oracle Database homes can be stored on Oracle ACFS only if the database version is Oracle Database 11g Release 2. Earlier releases of Oracle Database cannot be installed on Oracle ACFS because these releases were not designed to use Oracle ACFS.
Note:Before you start an Oracle RAC or Oracle Database install on an Oracle Clusterware release 11.2 installation, if you are upgrading from releases 220.127.116.11, 18.104.22.168, and 10.2.0.4, then Oracle recommends that you check for the latest recommended patches for the release you are upgrading from, and install those patches as needed on your existing database installations before upgrading.
For more information on recommended patches, refer to "Oracle Upgrade Companion," which is available through Note 785351.1 on My Oracle Support:
You can also refer to the Oracle Database Readme and Oracle Support Notes 756388.1 and 756671.1 for the current list of recommended patches for each release.
Use Oracle ASM Configuration Assistant (ASMCA) to create and modify disk groups when you install earlier Oracle Database and Oracle RAC releases on Oracle Grid Infrastructure 11g installations. Starting with Oracle Grid Infrastructure 11g Release 2, Oracle ASM is installed as part of an Oracle Grid Infrastructure installation, with Oracle Clusterware. You can no longer use Database Configuration Assistant (DBCA) to perform administrative tasks on Oracle ASM.
Before you use DBCA to create an Oracle RAC or Oracle Database 10.2.x or 11.1.x database on an Oracle Clusterware and Oracle ASM release 11.2 installation, you must install patches to the Oracle RAC or Oracle Database home. Refer to the Oracle Database Readme for information about specific patches.
If you are using Oracle Database 10g Release 2 software or Oracle Database 11g Release 1 software, then before you create a new database or apply any patches to your Oracle home, you must first stop the
OracleRemExecService Windows service on all the nodes in your cluster. If you do not stop this process before creating a database or applying patches to your Oracle home, then OPatch or DBCA fails to start the Oracle RAC database instances on the remote nodes. This failure causes the database creation or patching operation to return errors.
When Oracle Clusterware 11g Release 2 is installed on a cluster with no previous Oracle software version, it configures the cluster nodes dynamically, which is compatible with Oracle Database Release 11.2 and later, but Oracle Database 10g and 11.1 require a persistent configuration. Creating a persistent configuration for a node is called pinning a node.
Note:During an upgrade, all cluster member nodes are pinned automatically, and no manual pinning is required for existing databases. Pinning nodes is required only if you install earlier Oracle Database releases after installing Oracle Grid Infrastructure 11g Release 2 (11.2) software.
To pin a node in preparation for installing or using an earlier Oracle Database version, use
\bin\crsctl with the following format, 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
To determine if a node is in a pinned or unpinned state, use the
olsnodes -t -n
If you plan to create an Oracle Database 10g Release 2 on nodes
node4 of your cluster, then you need to pin those nodes. To pin nodes
node4, log in as an Administrator user and enter the following command:
C:\..\bin> crsctl pin css -n node3 node4
C:\> Grid_home\bin\olsnodes -t -n
This command produces output similar to the following:
node1 1 Pinned node2 2 Pinned node3 3 Pinned node4 4 Pinned
To list the state of a particular node use the
-n option with the
olsnodes command, where
Grid_home is the path for your Oracle Grid Infrastructure installation:
C:\> Grid_home\bin\olsnodes -t -n node3
This command produces output similar to the following:
node3 3 Pinned
See Also:Oracle Clusterware Administration and Deployment Guide for more information about pinning and unpinning nodes
To administer local and SCAN listeners using the Listener Control utility (LSNRCTL) in Oracle Clusterware and Oracle ASM 11g Release 2, use the
lsnrctl program located in the Grid home. Do not attempt to use the
lsnrctl programs from Oracle home locations for previous releases because they cannot be used with the new release.
Before shutting down Oracle Clusterware 11g Release 2, if you have an Oracle Database 10g Release 2 or Oracle Database 11g Release 1 database registered with Oracle Clusterware, then you must do one of the following:
Stop the Oracle Database 10g Release 2 or Oracle Database 11g Release 1 database instances first, then stop the Oracle Clusterware stack
crsctl stop crs -f command to shut down the Oracle Clusterware stack and ignore any errors that are raised
After installation, if you must modify the software installed in your Grid home, then you must first stop the Oracle Clusterware stack. For example, to apply a one-off patch or modify any of the dynamic-link libraries (DLLs) used by Oracle Clusterware or Oracle ASM, you must follow these steps to stop and restart Oracle Clusterware.
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:
Log in using a member of the Administrators group and go to the directory
Grid_home is the path to the Oracle Grid Infrastructure home.
Shut down Oracle Clusterware using the following command:
C:\..\bin> crsctl stop crs -f
After Oracle Clusterware is completely shut down, perform the updates to the software installed in the Grid home.
Use the following command to restart Oracle Clusterware:
C:\..\bin> crsctl start crs
Repeat steps 1 through 4 on each cluster member node.