This section lists special requirements for Sun Cluster Support for Oracle Parallel Server/Real Application Clusters.
Before you decide on which architecture to use for the Oracle components (Oracle UDLM and 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 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.
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,...) If you cannot find the Oracle log files at this location, contact Oracle support. This location is dependent on the Oracle UDLM package.
Oracle UDLM logs – /var/cluster/ucmm/dlm_nodename/logs
Oracle UDLM core files – /var/cluster/ucmm/dlm_nodename/cores
If a node fails in an Oracle Parallel Server/Real Application Clusters environment, you can configure Oracle clients to reconnect to the surviving server without the use of the IP failover that Sun Cluster failover data services use. The Sun Cluster 3.1 Concepts Guide document describes this failover process. In an Oracle Parallel Server/Real Application Clusters environment, multiple Oracle instances cooperate to provide access to the same shared database. The Oracle clients can use any of the instances to access the database. Thus, if one or more instances have failed, clients can connect to a surviving instance and continue to access the database.
If a node fails, boot the node into maintenance mode to correct the problem. See the Sun Cluster 3.1 System Administration Guide for more information.
When you install this data service, ensure that you complete all steps of all procedures that precede How to Install the Oracle RDBMS Software and Create Your Oracle Database before you reboot the nodes. Otherwise, the nodes will panic. If the nodes panic, you must boot into maintenance mode to correct the problem.
Note the following points if you plan to use the Oracle Parallel Fail Safe/Real Application Clusters Guard option with Sun Cluster 3.1.
If you use this option, before you install Sun Cluster 3.1, you must consider the following special requirement. Hostnames that you use in your cluster cannot contain special characters. You cannot change the hostname after you install Sun Cluster 3.1. See the Oracle documentation for more information about this special requirement and any others before you install Sun Cluster 3.1.
Refer to the Oracle documentation for installation, administration and operation of this product option.
Do not use Sun Cluster commands to manipulate the state of resources that Oracle Parallel Fail Safe/Real Application Clusters Guard installs. To do so might result in failures. Do not rely on the Sun Cluster commands to query the state of the resources that Oracle Parallel Fail Safe/Real Application Clusters Guard installs. This state may not reflect the actual state. To check the state of the Oracle Parallel Fail Safe/Real Application Clusters Guard, use the commands that Oracle supplies.