Sun Cluster Data Service for Oracle Real Application Clusters Guide for Solaris OS

Special Requirements

This section lists special requirements for Sun Cluster Support for Oracle Real Application Clusters.

32-Bit Mode or 64-Bit Mode

Before you decide which architecture to use for the Oracle UDLM and the Oracle relational database management system (RDBMS), note the following points.

The architecture of both Oracle components must match. For example, if you have 64-bit architecture for your Oracle UDLM, you must have 64-bit architecture for your RDBMS.
If you have 32-bit architecture for your Oracle components, you can boot the node on which the components reside in either 32-bit mode or 64-bit mode. However, if you have 64-bit architecture for your Oracle components, you must boot the node on which the components reside in 64-bit mode.
You must use the same architecture when you boot all of the nodes. For example, if you boot one node to use 32-bit architecture, you must boot all of the nodes to use 32-bit architecture.

Log File Locations

The following list shows the locations of the data service log files.

Current log: /var/cluster/ucmm/ucmm_reconf.log
Previous logs: /var/cluster/ucmm/ucmm_reconf.log.0 (0,1,...) – This location is dependent on the Oracle UDLM package.
Oracle UDLM logs: /var/cluster/ucmm/dlm_nodename/logs – If you cannot find the Oracle log files at this location, contact Oracle support.
Oracle UDLM core files: /var/cluster/ucmm/dlm_nodename/cores – If you cannot find the Oracle log files at this location, contact Oracle support.
Logs for Oracle RAC server resource: /var/opt/SUNWscor/oracle_server

Rebooting Nodes During the Installation of Sun Cluster Support for Oracle Real Application Clusters

During installation of this data service, reboot the nodes only after you have installed and configured the Oracle UDLM software, and satisfied the prerequisites for performing this task. Otherwise, the nodes panic.

For information about how to recover from a node panic during installation, see Node Panic During Initialization of Sun Cluster Support for Oracle Real Application Clusters.

Using the Oracle Real Application Clusters Guard Option With Sun Cluster 3.1

For information about the installation, administration, and operation of the Oracle Real Application Clusters Guard option, see the Oracle documentation. If you plan to use this product option with Sun Cluster 3.1, note the points in the subsections that follow before you install Sun Cluster 3.1.

Hostname Restrictions

If you use the Oracle Real Application Clusters Guard option with Sun Cluster 3.1, the following restrictions apply to hostnames that you use in your cluster:

Hostnames cannot contain special characters.
You cannot change the hostnames after you install Sun Cluster 3.1.

For more information about these restrictions and any other requirements, see the Oracle documentation.

Sun Cluster Command Usage Restrictions

If you use the Oracle Real Application Clusters Guard option with Sun Cluster 3.1, do not use Sun Cluster commands to perform the following operations:

Manipulating the state of resources that Oracle Real Application Clusters Guard installs. Using Sun Cluster commands for this purpose might cause failures.
Querying the state of the resources that Oracle Real Application Clusters Guard installs. This state might not reflect the actual state. To check the state of the Oracle Real Application Clusters Guard, use the commands that Oracle supplies.