JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
Oracle Solaris Cluster Data Service for Sybase ASE Guide
search filter icon
search icon

Document Information

Preface

1.  Installing and Configuring Solaris Cluster HA for Sybase ASE

Solaris Cluster HA for Sybase ASE Overview

Overview of Installing and Configuring Solaris Cluster HA for Sybase ASE

Preparing to Install Solaris Cluster HA for Sybase ASE

Installing the Sybase ASE Software

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

How to Install the Sybase ASE Software

How to Verify the Sybase ASE Installation

Configuring Sybase ASE Database Access and Creating the Sybase ASE Database Environment

How to Configure Sybase ASE Database Access With Solaris Volume Manager

How to Configure Sybase ASE Database Access With Veritas Volume Manager

How to Create the Sybase ASE Database Environment

Installing the Solaris Cluster HA for Sybase ASE Packages

How to Install the Solaris Cluster HA for Sybase ASE Packages

Registering and Configuring Solaris Cluster HA for Sybase ASE

Setting Solaris Cluster HA for Sybase ASE Extension Properties

How to Register and Configure Solaris Cluster HA for Sybase ASE

Verifying the Solaris Cluster HA for Sybase ASE Installation and Configuration

How to Verify the Solaris Cluster HA for Sybase ASE Installation and Configuration

Location of Solaris Cluster HA for Sybase ASE Log Files

Solaris Cluster HA for Sybase ASE Logging and Security Issues

Solaris Cluster HA for Sybase ASE Logging Issues

Solaris Cluster HA for Sybase ASE Security Issues

Tuning the Solaris Cluster HA for Sybase ASE Fault Monitor

Main Fault-Monitor Process

Database-Client Fault Probe

Obtaining Core Files for Troubleshooting

Customizing the Solaris Cluster HA for Sybase ASE Fault Monitor

Defining Custom Behavior for Errors

Custom Action File Format

Changing the Response to a DBMS Error

Responding to an Error Whose Effects Are Major

Ignoring an Error Whose Effects Are Minor

Changing the Response to Logged Alerts

Changing the Maximum Number of Consecutive Timed-Out Probes

Propagating a Custom Action File to All Nodes in a Cluster

Specifying the Custom Action File That a Server Fault Monitor Should Use

How to Specify the Custom Action File That a Server Fault Monitor Should Use

A.  Solaris Cluster HA for Sybase ASE Extension Properties

B.  Preset Actions for DBMS Errors and Sybase ASE Logged Alerts

Index

Installing the Sybase ASE Software

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


Note - Before you configure Solaris Cluster HA for Sybase ASE, use the procedures that the Oracle Solaris Cluster Software Installation Guide describes to configure the Oracle Solaris Cluster software on each node.



Note - The Solaris Cluster HA for Sybase ASE can be configured to run in a whole root or a sparse root non-global zone for x86/x64 and SPARC architectures.


How 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 or zones. If you do not perform all of the steps on all of the nodes or zones, the Sybase ASE installation will be incomplete, and Solaris 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 Solaris Cluster HA for Sybase ASE starts and stops correctly if a switchover or failover occurs.

    On each node or zone that can master the logical host that runs Solaris Cluster HA for Sybase ASE, include the following entries in the /etc/nsswitch.conf file.

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

    Solaris 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 Solaris 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 Oracle Solaris Cluster Software Installation Guide.


    Note - Configuring raw devices on non-global zones is not supported on Oracle Solaris Cluster.


    If you use the 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 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 or zone, 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 or zones that run Solaris 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 or zone, 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 or zones that run Solaris Cluster HA for Sybase ASE.

How to Install the Sybase ASE Software

  1. On a cluster node or zone, become superuser 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 Solaris Cluster HA for Sybase ASE.

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

    Specifies an optional, comma-separated list of physical node names or zones or IDs that identify potential masters. The order here determines the order in which the Resource Group Manager (RGM) considers primary nodes or zones 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 Solaris 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.
    # 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 host name 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 or zone 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 or zone 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 or zone 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.

How to Verify the Sybase ASE Installation

Next Steps

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