test

Sun Cluster Data Service for Sybase ASE Guide for Solaris OS

Installing the Sybase ASE 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 Software Installation Guide for Solaris OS describes to configure the Sun Cluster software on each node.

ProcedureHow to Prepare the Nodes for the Installation of the Sybase ASE Software

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.

Steps

  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 the following entries in the /etc/nsswitch.conf file.

    passwd:    files nis [TRYAGAIN=0]
publickey: files nis [TRYAGAIN=0]
project:   files nis [TRYAGAIN=0]
group:     files

    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 the preceding entries 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. For information about how to configure global devices, see Sun Cluster Software Installation Guide for Solaris OS.

    If you use the Solstice DiskSuiteTM/Solaris Volume Manager software, configure the Sybase ASE software to use UNIX file system (UFS) logging on mirrored metadevices or raw-mirrored metadevices. For information about how to configure raw-mirrored metadevices, see the Solstice DiskSuite/Solaris Volume Manager documentation.

  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 being overwritten during reinstallation of the operating system.

  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 create entries this way, 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.

ProcedureHow to Install the Sybase ASE Software

Steps

  1. Become superuser on a cluster member.

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

    If you plan to install the Sybase ASE software at another location, omit this step.

    For more information about installation locations, see Preparing to Install Sun Cluster HA for Sybase ASE.

  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 host name 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 host name 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 support the use of the adapter name for netif.

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

    • Enabling the resource and fault monitoring

    • Moving the resource group into a managed state

    • Bringing the resource group online


    # scswitch -Z -g resource-group

  7. On the node that masters the resource group that you just created, log in 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 about how to install the Sybase ASE software, refer to the Sybase installation and configuration guides.

  9. For every Sybase ASE server, specify the host name that is associated with a network resource.

    If you do not specify a host name that is associated with a network resource, Sybase ASE starts only on the node where the Sybase ASE software was installed.

    Some versions of Sybase ASE, such as 12.5, prompt you for the host name. Other versions of Sybase ASE, such as 12.5.1, use the physical host name. If your version of Sybase ASE uses the physical host name, you must change the physical host name to specify a network resource.

    • If the Sybase ASE installer prompts you for the host name, type the host name in response to the prompt.

    • Otherwise, modify the interfaces file to change the physical host name to a host name that is associated with a network resource.

Next Steps

After you install the Sybase ASE software, go to How to Verify the Sybase ASE Installation.

ProcedureHow to Verify the Sybase ASE Installation

Steps

  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.

Next Steps

After you verify the Sybase ASE installation, go to Configuring Sybase ASE Database Access and Creating the Sybase ASE Database Environment.