test

Sun Cluster 3.0 U1 Data Services Installation and Configuration Guide

How to Prepare the Nodes

This procedure describes how to prepare the cluster nodes for installation of the Oracle application software.

Caution - Caution -

Perform all the steps described in this section on all Sun Cluster nodes. If you do not perform all steps on all nodes, the Oracle installation will be incomplete, and the Sun Cluster HA for Oracle data service will fail during startup.

Note -

Consult the Oracle documentation before you perform this procedure.

The following steps prepare Sun Cluster nodes and install the Oracle software.

  1. Become superuser on all the cluster members.

  2. Configure the /etc/nsswitch.conf files as follows so that the data service starts and stops correctly if a switchover or failover occurs.

    On each node that can master the logical host that runs the Sun Cluster HA for Oracle data service, include one of the following entries for group in the /etc/nsswitch.conf file.


    group:
group:		 	files
group:		 	files [NOTFOUND=return] nis
group:		 	files [NOTFOUND=return] nisplus

    The Sun Cluster HA for Oracle data service uses the su user command to start and stop the database node. The network information name service might become unavailable when a cluster node's public network fails. Adding one of the preceding entries for group ensures that the su(1M) command does not refer to the NIS/NIS+ name services if the network information name service is unavailable.

  3. Configure the cluster file system for the Sun Cluster HA for Oracle data service.

    If raw devices contain the databases, configure the global devices for raw-device access. See the Sun Cluster 3.0 U1 Installation Guide for information on how to configure global devices.

    When you use the SolsticeTM DiskSuite volume manager, configure the Oracle software to use UNIX file system (UFS) logging or raw-mirrored meta devices. See the Solstice DiskSuite documentation for more information on how to configure raw-mirrored meta devices.

  4. Prepare the $ORACLE_HOME directory on a local or multihost disk.

    Note -

    If you install the Oracle binaries on a local disk, use a separate disk if possible. Installing the Oracle binaries on a separate disk prevents the binaries from overwrites during operating environment reinstallation.

  5. On each node, create an entry for the database administrator group (DBA) in the /etc/group file, and add potential users to the group.

    You typically name the DBA group dba. Verify that the root and oracle_id users are members of the dba group, and add entries as necessary for other DBA users. Ensure that the group IDs are the same on all the nodes that run the Sun Cluster HA for Oracle data service, as the following example illustrates.


    dba:*:520:root,oracle

    You can create group entries in a network name service (for example, NIS or NIS+). If you do so, add your entries to the local /etc/inet/hosts file to eliminate dependency on the network name service.

  6. On each node, create an entry for the Oracle user ID (oracle_id).

    You typically name the Oracle user ID oracle. The following command updates the /etc/passwd and /etc/shadow files with an entry for the Oracle user ID.


    # useradd -u 120 -g dba -d /Oracle-home oracle

    Ensure that the oracle_id user entry is the same on all the nodes that run the Sun Cluster HA for Oracle data service.