Sun Cluster 3.1 Data Service for Oracle Parallel Server/Real Application Clusters Guide

Special Requirements

This section lists special requirements for Sun Cluster Support for Oracle Parallel Server/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.

Log File Locations

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

Node Failures and Recovery Procedures

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.


Note –

If a node fails, boot the node into maintenance mode to correct the problem. After you have corrected the problem, reboot the node. See the Sun Cluster 3.1 10/03 System Administration Guide for more information.



Note –

When you install this data service, ensure that you complete all steps of all procedures that precede installing the Oracle RDBMS software and creating 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. After you have corrected the problem, you must reboot the nodes. The procedures that you must complete are listed in Table 2–1.


Using the Sun Cluster LogicalHostname Resource With Oracle Parallel Server/Real Application Clusters

If a cluster node that is running an instance of Oracle Parallel Server/Real Application Clusters fails, an operation that a client application attempted might be required to time out before the operation is attempted again on another instance. If the Transmission Control Protocol/Internet Protocol (TCP/IP) network timeout is high, the client application might require a significant length of time to detect the failure. Typically, client applications require between three and nine minutes to detect such failures.

In such situations, client applications can use the Sun Cluster LogicalHostname resource for connecting to an Oracle Parallel Server/Real Application Clusters database that is running on Sun Cluster. You can configure the LogicalHostname resource in a separate resource group that is mastered on the nodes on which Oracle Parallel Server/Real Application Clusters is running. If a node fails, the LogicalHostname resource fails over to another surviving node on which Oracle Parallel Server/Real Application Clusters is running. The failover of the LogicalHostname resource enables new connections to be directed to the other instance of Oracle Parallel Server/Real Application Clusters.


Caution – Caution –

Before using the LogicalHostname resource for this purpose, consider the effect on existing user connections of failover or failback of the LogicalHostname resource.


Using the Oracle Parallel Fail Safe/Real Application Clusters Guard Option With Sun Cluster 3.1

For information about the installation, administration, and operation of the Oracle Parallel Fail Safe/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 Parallel Fail Safe/Real Application Clusters Guard option with Sun Cluster 3.1, the following restrictions apply to hostnames that you use in your cluster:

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

Sun Cluster Command Usage Restrictions

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