8 Oracle Grid Infrastructure Postinstallation Procedures

8.1.1 Download and Install Patch Updates

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

https://support.oracle.com

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 release number e.g. 11.2.0.1.0 to 11.2.0.3.0, these patch sets are fully regression tested in the same way that the base release is (i.e. 11.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 11.2.0.1 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 the 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.

Refer to Appendix D, "How to Upgrade to Oracle Grid Infrastructure 12c Release 1" for information about how to stop database processes in preparation for installing patches.

8.1.2 Configure the Oracle ARP Driver

Oracle Grid Infrastructure on Windows Server 2008 or Windows Server 2008 R2 requires the Oracle Address Resolution Protocol (ARP) driver.

1. Start the Oracle Grid Infrastructure stack, if it is not started.

   To check the status of the Oracle Grid Infrastructure stack, use:

   crsctl check crs
   

   To start the Oracle Grid Infrastructure stack, use:

   crsctl start crs
   

2. Use the netcfg utility to install the Oracle ARP driver, as shown in the following command:

   %systemroot%\system32\netcfg.exe -l Grid_home\bin\oraarpdrv.inf -c p 
   -i orcl_ndisprot
   

   If "Oracle America, Inc." is not in list of the trusted publishers for the node, then select Install to allow the installation to continue.

3. Configure the Oracle ARP driver to start automatically following system restarts:

   sc config oraarpdrv start= auto
   

4. Start the Oracle ARP Protocol Driver.

   net.exe start oraarpdrv
   

5. Stop the following Oracle Clusterware resources:

   1. If GNS is configured for your cluster, then stop the GNS resource:

      Grid_home\bin\srvctl stop gns
      

      To determine if GNS is configured for your cluster, use the following command:

      Grid_home\bin\srvctl config gns
      

   2. Stop the SCAN resource.

      Grid_home\bin\srvctl stop scan -f
      

   3. Stop all node applications running on the cluster.

      Grid_home\bin\srvctl stop nodeapps -n nodename -f
      

6. Restart the Oracle Clusterware resources in the opposite order.

   1. Start all node applications running on the cluster.

      Grid_home\bin\srvctl start nodeapps -n nodename
      

   2. Start the SCAN resource.

      Grid_home\bin\srvctl start scan
      

   3. If GNS is configured for your cluster, then start the GNS resource:

      Grid_home\bin\srvctl start gns
      

8.1.3 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 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 executable files 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 file. If you choose the create the exception in this way, the effect is the same as creating an exception for the executable file either through Control Panel or from the command line.

The following sections list the Oracle Database 11g release 2 (11.2) executable files that listen on TCP ports on Windows, along with a brief description of the executable file. It is recommended that these executable files (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 file, for example, oracle.exe, multiple times, once for each Oracle home from which that executable file loads.

• Firewall Exceptions for Oracle Database

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

• Firewall Exceptions for Oracle Gateways

• Firewall Exceptions for Oracle Clusterware and Oracle ASM

• Firewall Exceptions for Oracle RAC Database

• Firewall Exceptions for Other Oracle Products

8.2.1 Optimize Memory Usage for Programs

The Windows operating system should be optimized for Memory Usage of 'Programs' instead of 'System Caching'.

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, ensure Programs is selected.

8.2.2 Create a Fast Recovery Area Disk Group

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.

8.2.3 Checking the SCAN Configuration

The SCAN is a name that provides 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 run a particular database instance. Clients can continue to access the cluster in the same way as with earlier releases, but Oracle recommends that clients accessing the cluster use the SCAN.

After installation, when a client sends a request to the cluster, the Oracle Clusterware SCAN listeners redirect client requests to servers in the cluster.

You can use the command cluvfy comp scan (located in Grid_home\bin) to confirm that the DNS is correctly associating the SCAN with the addresses. For example:

C:\> cluvfy comp scan
Verifying scan

Checking Single Client Access Name (SCAN)...

Checking TCP connectivity to SCAN Listeners...
TCP connectivity to SCAN Listeners exists on all cluster nodes

Checking name resolution setup for "node1.example.com"...

Verification of SCAN VIP and Listener setup passed

Verification of scan was successful.

8.4.1 General Restrictions for Using Earlier Oracle Database Releases

You can use Oracle Database 10g and Oracle Database 11g with Oracle Clusterware and Oracle ASM 12c Release 1 (12.1). If you upgrade an existing release of Oracle Clusterware and Oracle ASM to Oracle Grid Infrastructure 11g Release 2 (11.2) (which includes Oracle Clusterware and Oracle ASM), and you also plan to upgrade your Oracle RAC database to Oracle Database 12c Release 1 (12.1), 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.

However, if you upgrade to Oracle Grid Infrastructure 12c Release 1 (12.1), and you have existing Oracle RAC installations that you do not plan to upgrade, or if you install an earlier release of Oracle RAC (11.2) on a cluster running Oracle Grid Infrastructure 12c Release 1 (12.1), then you must complete additional configuration tasks or apply patches, or both, before the earlier database releases will work correctly with Oracle Grid Infrastructure.

Oracle Database homes can only be stored on Oracle ACFS if the database release is Oracle Database 11g Release 2 or higher. Earlier releases of Oracle Database cannot be installed on Oracle ACFS because these releases were not designed to use Oracle ACFS.

8.4.2 Using ASMCA to Administer Disk Groups for Earlier Database Releases

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.

• 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.

8.4.3 Using the Correct LSNRCTL Commands

Do not attempt to use the lsnrctl programs from Oracle home locations for earlier releases because they cannot be used with the new release.

• Use the Listener Control utility, lsnrctl, located in the Oracle Grid Infrastructure 12c home to administer local and SCAN listeners for Oracle Clusterware and Oracle ASM 11g Release 2.

8.4.4 Starting and Stopping Cluster Nodes or Oracle Clusterware Resources

Before shutting down Oracle Clusterware 12c Release 1 (12.1), if you have an Oracle Database 11g Release 2 (11.2) database registered with Oracle Clusterware, then you must do one of the following:

• Stop the Oracle Database 11g Release 2 database instances first, then stop the Oracle Clusterware stack

• Use the crsctl stop crs -f command to shut down the Oracle Clusterware stack and ignore any errors that are raised

If you need to shut down a cluster node that currently has Oracle Database and Oracle Grid Infrastructure running on that node, then you must perform the following steps to cleanly shutdown the cluster node:

• Use the crsctl stop crs command to shut down the Oracle Clusterware stack

• After Oracle Clusterware has been stopped, you can shutdown the Windows server using shutdown -r.