Oracle® Database

3.1 Oracle Real Application Clusters (RAC) Support

The list of supported installation options and supported storage types for Oracle Clusterware, Oracle Real Application Clusters, and vendor clusterware are described in this section. Oracle plans to support additional Oracle Clusterware and RAC configurations in the future. Please check for updates to this document for the latest list of supported installation scenarios on the OTN Web site at:

http://www.oracle.com/technology/documentation/

Supported Oracle Real Application Clusters Configurations at the Time of This Publication

Oracle supports the software and storage configurations shown in the following table:

^Footnote 1 For Oracle Clusterware, the stored files are the OCR and voting disk; for RAC, the stored files are the database files.

3.2 Adding a Node to a Shared Oracle Clusterware Configuration

Before running root.sh in the first node of a shared Oracle Clusterware home, add the following line in the $ORA_CRS_HOME/opmn/conf/ons.config file:

usesharedinstall=true

This issue is tracked with Oracle bug 4454562.

3.3 Installing Oracle Security Manager

To install Oracle Security Manager, install Oracle Client and choose the Administrator installation type.

3.4 Installing Oracle Database on a Computer With an Existing Automatic Storage Management Instance

Oracle Universal Installer displays an error message that reads 0. This message is displayed after you specify the database home and path in the Specify Home Details screen and click Next. Ignore the error message whenever it is displayed, and continue the installation.

3.5 Modifying a Virtual IP Address Node Application

When modifying the name, IP address, or netmask of an existing virtual IP address (VIP) resource, run the following command:

srvctl modify nodeapps

and include the existing interfaces for the VIP in the -A argument. For example:

srvctl modify nodeapps -n mynode1 -A 100.200.300.40/255.255.255.0/eth0

This issue is tracked with Oracle bug 4500688.

3.6 Pinging the Gateway for VIP Address

In Chapter 2, Preinstallation, the section IP Address Requirements contains the following sentence:

During installation, OUI pings the VIP, so ensure that the VIP responds to a ping command before starting installation.

This information is incorrect. The following is the correct information:

During installation, OUI pings the gateway to ensure that the VIP is reachable. Therefore, you should ensure that the default gateway responds to a ping command. To find the default gateway, use the route command. Refer to your operating system help for details.

3.7 listener.ora File Corrections

In Chapter 9, Understanding the Oracle Real Application Clusters Installed Configuration, the section "How Oracle Uses the Listener (listener.ora File)" contains a sample listener.ora file. The parameter entry, (IP=FIRST), should be added to the second address parameter of the listener_node1 definition. Additionally, two closing parentheses are required at the end of the sid_list_listener_node1 definition. The revised example should look like this:

listener_node1=
   (description=
    (address=(protocol=ipc)(key=extproc))
    (address=(protocol=tcp)(host=node1-vip)(port=1521)(IP=FIRST))
    (address=(protocol=tcp)(host=node1-ip)(port=1521)))
sid_list_listener_node1=
   (sid_list=
     (sid_desc=
      (sid_name=plsextproc)
       (oracle_home=/private/system/db)
      (program=extproc)))

7.1 Materialized View and Partition Change Tracking Rewrite

When the query has single column in-lists, the materialized view has ranges, and partition change tracking rewrite is used, you might get stale results with Query Rewrite. Turn off the fresh partition containment rewrite to avoid this problem by using the following command:

SQL> alter session set "_query_rewrite_fpc" = false;

7.2 Host-Based Mirroring

The host-based mirroring is not supported with ASM. Note that there is no issue with resilvering for storage based mirroring.

Workaround: Use ASM redundancy.

This issue is tracked with Oracle bug 4466206.

7.3 Oracle ODBC Driver Limitations

Oracle ODBC driver for Solaris does not work if you use the REAL data type for a column and the application tries to retrieve data as native double or float data type through PL/SQL stored procedure.

Workaround: Instead of the REAL data type, use the NUMBER(s,p) data type while creating a table.

This issue is tracked with Oracle bug 4551566.

7.4 Importing a User Certificate Into Oracle Wallet Using Oracle Wallet Manager

Oracle Wallet Manager will fail to recognize the user certificate as valid if you capture the user certificate contents from the Oracle Certificate Authority site and save this as a flat file. This is because when saving as a flat file, all the lines of the user certificate are run together with no line breaks.

Workaround: Edit the user certificate. Insert a new line after -----BEGIN CERTIFICATE----- and a new line before -----END CERTIFICATE-----.

7.5 Removing Metrics for Wait Classes Removes Them Permanently

Do not remove the key values for the wait class metrics. Doing so removes them permanently and currently there is no easy way to recover them.

This issue is tracked with Oracle bug 4602952.