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 Sybase ASE software installation.

Caution - Caution -

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

Note -

Consult the Sybase ASE documentation before you perform this procedure.

  1. Become superuser on all nodes.

  2. Configure the /etc/nsswitch.conf file as follows so that the Sun Cluster HA for Sybase ASE 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 Sybase ASE data service, include one of the following entries for group in the /etc/nsswitch.conf file.


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

    The Sun Cluster HA for Sybase ASE data service uses the su user command to start and stop the database node. The user is typically sybase_id. 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 Sybase ASE 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.

    If you use the Solstice DiskSuite volume manager, configure the Sybase ASE software to use UNIX file system (UFS) logging or raw-mirrored metadevices. See the Solstice DiskSuite documentation for information on how to configure raw-mirrored metadevices.

  4. Prepare the SYBASE_HOME directory on a local or multihost disk.

    Note -

    If you install the Sybase ASE binaries on a local disk, use a separate disk if possible. Installing the Sybase ASE 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 (DBA) group in the /etc/group file, and add potential users to the group.

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


    dba:*:520:root,sybase_id

    You can create group entries in a network name service. If you do so, also 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 Sybase system administrator.

    You typically name the Sybase system administrator sybase_id. The following command updates the /etc/passwd and /etc/shadow files with an entry for the Sybase system administrator.


    # useradd -u 120 -g dba -d /Sybase-home sybase_id

    Make sure that the sybase_id user entry is the same on all nodes that run the Sun Cluster HA for Sybase ASE data service.