Oracle RAC Support

Note: Refer to the Oracle Real Application Clustering (RAC) documentation for setup instructions and parameter settings for RAC. It is assumed that RAC is installed, including Oracle Notification Service (ONS) for Fast Connection Failover support and configured prior to configuration of Oracle Utilities Work and Asset Management to take advantage of the RAC installation.

Oracle Utilities Work and Asset Management supports the use of Oracle's Real Application Clustering (RAC) for high availability and performance through database clustering. Oracle Utilities Work and Asset Management has additional setting to tell the database pooling aspects of the product to take advantage of the RAC facilities.

Once RAC has been installed and configured on the database there are a number of options that can be used to configure the product to use RAC in all modes of configuration:

• It is possible to set up a custom DB Connection string to take advantage of the RAC as outlined in the Overriding the Default Oracle Database Connection Information section of this document. This is the easiest implementation of RAC but does not take advantage of the full RAC features.

Configure RAC specific settings in the installation configuration files through the configureEnv.sh utility. See configureEnv – Set up Environment Settings. The following settings should be set:

Environment Settings	Usage	Comments
ONS_JAR_DIR	Location of ONS Jar file (ons.jar)	This is the location of the Oracle Notification Service Jar files for use in the product.
ONSCONFIG	ONS configuration string with RAC server nodes delimited by "," in the form <host>:<port> where <host> is the RAC host node and <port> is the ONS listener port.	Used for connections.

Note: Native RAC Support does not support XA transactions using Universal Connection Pool (UCP) at the present time. If XA compliance is required, it is suggested that JNDI based pools provided by the web application server be used as documented in Using JNDI Based Data Sources.

Note: At the present time Oracle Single Client Access Name (SCAN) is not supported in the configuration of RAC native support.

Note: Once configured the spl.runtime.options.isFCFEnabled is set to true and spl.runtime.options.onsserver is set to the value specified in ONSCONFIG.

Note: Support for Implicit Connection Caching has been removed as this feature has been superseded by Universal Connection Pool (UCP).