test

Sun Cluster 3.1 Data Service for Sybase ASE Guide

Installing the Sybase ASE 12.0 Software

Use the procedures in this section to complete the following tasks.

Note –

Before you configure Sun Cluster HA for Sybase ASE, use the procedures that the Sun Cluster 3.1 Software Installation Guide describes to configure the Sun Cluster software on each node.

How to Prepare the Nodes

This procedure describes how to prepare the cluster nodes for Sybase ASE software installation.

Caution – Caution –

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

Note –

Consult the Sybase ASE documentation before you perform this procedure.

  1. Become superuser on all of the nodes.

  2. Configure the /etc/nsswitch.conf file as follows so that Sun Cluster HA for Sybase ASE starts and stops correctly if a switchover or failover occurs.

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


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

    Sun Cluster HA for Sybase ASE 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 Sun Cluster HA for Sybase ASE.

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

    If you use the Solstice DiskSuiteTM/Solaris Volume Manager software, configure the Sybase ASE software to use UNIX file system (UFS) logging on mirrored meta devices or raw-mirrored meta devices. See the Solstice DiskSuite/Solaris Volume Manager 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.

    Verify that the root and sybase users are members of the dba group, and add entries as necessary for other DBA users. Ensure that group IDs are the same on all of the nodes that run Sun Cluster HA for Sybase ASE, as the following example illustrates.


    dba:*:520:root,sybase

    You can create group entries in a network name service. If you do so, also add your entries to the local /etc/group file to eliminate dependency on the network name service.

  6. On each node, create an entry for the Sybase system administrator.

    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

    Ensure that the sybase user entry is the same on all of the nodes that run Sun Cluster HA for Sybase ASE.

How to Install the Sybase ASE Software

Perform the following steps to install the Sybase ASE software.

  1. Become superuser on a cluster member.

  2. Note the Sybase ASE installation requirements.

    You can install Sybase ASE binaries on one of the following locations.

    • Local disks of the cluster nodes

    • Highly available local file system

    • Cluster file system

      Note –

      Before you install the Sybase ASE software on the cluster file system, start the Sun Cluster software and become the owner of the disk device group.

    See Preparing to Install Sun Cluster HA for Sybase ASE for more information about installation locations.

  3. Create a failover resource group to hold the network and application resources.


    # scrgadm -a -g resource-group [-h nodelist]
    -g resource-group

    Specifies the name of the resource group. This name can be your choice but must be unique for resource groups within the cluster.

    -h nodelist

    Specifies an optional, comma-separated list of physical node names or IDs that identify potential masters. The order here determines the order in which the Resource Group Manager (RGM) considers primary nodes during failover.

    Note –

    Use the -h option to specify the order of the node list. If all of the nodes in the cluster are potential masters, you do not need to use the -h option.

  4. Verify that you have added all of the network resources that Sun Cluster HA for Sybase ASE uses to either the /etc/inet/hosts file or to your name service (NIS, NIS+) database.

  5. Add a network resource (logical hostname or shared address) to the failover resource group.


    # scrgadm -a -L -g resource-group -l logical-hostname [-n netiflist]
    -l logical-hostname

    Specifies a network resource. The network resource is the logical hostname or shared address (IP address) that clients use to access Sun Cluster HA for Sybase ASE.

    -n netiflist

    Specifies an optional, comma-separated list that identifies the IP Networking Multipathing groups that are on each node. Each element in netiflist must be in the form of netif@node. netif can be given as an IP Networking Multipathing group name, such as sc_ipmp0. The node can be identified by the node name or node ID, such as sc_ipmp0@1 or sc_ipmp@phys-schost-1.

    Note –

    Sun Cluster does not currently support using the adapter name for netif.

  6. Run the scswitch(1M) command to complete the following tasks.

    • Enable the resource and fault monitoring.

    • Move the resource group into a managed state.

    • Bring the resource group online.


    # scswitch -Z -g resource-group

  7. On the node mastering the resource group that you just created, login as sybase.

    The installation of the Sybase binaries must be performed on the node where the corresponding logical host is running.

  8. Install the Sybase ASE software.

    Regardless of where you install the Sybase ASE software, modify each node's /etc/system files as you would in standard Sybase ASE installation procedures. For instructions on how to install the Sybase ASE software, refer to the Sybase installation and configuration guides.

    Note –

    For every Sybase server, enter the hostname that is associated with a network resource when asked to specify the hostname.

Where to Go From Here

After you install the Sybase ASE software, go to How to Configure Sybase ASE Database Access With Solstice DiskSuite/Solaris Volume Manager if you use the Solstice DiskSuite/Solaris Volume Manager. Go to How to Configure Sybase ASE Database Access With VERITAS Volume Manager if you use the VERITAS Volume Manager (VxVM).

How to Verify the Sybase ASE Installation

Perform the following steps to verify the Sybase ASE software installation.

  1. Verify that the sybase user and the dba group own the $SYBASE_HOME directory and $SYBASE_HOME children directories.

  2. Run the scstat(1M) command to verify that the Sun Cluster software functions correctly.