Oracle® Solaris Cluster Data Service for Sybase ASE Guide

Exit Print View

Updated: July 2014, E39577–01
 
 

How to Install the Sybase ASE Software

Before You Begin

Ensure that the /etc/netmasks file has IP-address subnet and netmask entries for all logical hostnames. If necessary, edit the /etc/netmasks file to add any missing entries.

  1. On a cluster node, assume the root role or assume a role that provides solaris.cluster.modify and solaris.cluster.admin RBAC authorizations.
  2. If you plan to install the Sybase ASE software on the cluster file system, start the Oracle Solaris 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 HA for Sybase ASE.

  3. Create a failover resource group to hold the network and application resources.
    # clresourcegroup create [-n nodelist] resource-group
    -n nodelist

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

    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.


    Note -  Use the -n 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 -n option.
  4. Verify that you have added all of the network resources that 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.
    # clreslogicalhostname create -g resource-group -h host_list logical_host
    logical_host

    Specifies a resource name of your choice.

    host_list

    Specifies a comma-separated list of host names that are to be made available by the logical hostname resource.

  6. Run the clresourcegroup (1CL) 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

    # clresourcegroup online -M 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 prompt you for the host name. Other versions of Sybase ASE 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.


    Note -  For a licensed version of Sybase ASE, the host name that you specify must be associated with a valid license file.

Next Steps

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