Installing and Configuring Sun Cluster HA for Sybase ASE

This chapter provides instructions on how to configure and administer Sun Cluster HA for Sybase ASE on your Sun Cluster nodes.

This chapter contains the following procedures.

• How to Prepare the Nodes

• How to Install the Sybase ASE Software

• How to Verify the Sybase ASE Installation

• How to Configure Sybase ASE Database Access With Solstice DiskSuite/Solaris Volume Manager

• How to Configure Sybase ASE Database Access With VERITAS Volume Manager

• How to Create the Sybase ASE Database Environment

• How to Install the Sun Cluster HA for Sybase ASE Packages by Using the Web Start Program

• How to Install Sun Cluster HA for Sybase ASE Packages by Using the scinstall Utility

• How to Register and Configure Sun Cluster HA for Sybase ASE

• How to Verify the Sun Cluster HA for Sybase ASE Installation

You must configure Sun Cluster HA for Sybase ASE as a failover data service. See the Sun Cluster Concepts Guide for Solaris OS document and “Planning for Sun Cluster Data Services” in Sun Cluster Data Services Planning and Administration Guide for Solaris OS for general information about data services, resource groups, resources, and other related topics.

Installing and Configuring Sun Cluster HA for Sybase ASE

The following table lists sections that describe the installation and configuration tasks.

Preparing to Install Sun Cluster HA for Sybase ASE

To prepare your nodes for the Sun Cluster HA for Sybase Adaptive Server 12.0 installation, select an installation location for the following files.

• Sybase ASE application files – These files include Sybase ASE binaries and libraries. You can install these files on either the local file system or the cluster file system.

  See “Configuration Guidelines for Sun Cluster Data Services” in Sun Cluster Data Services Planning and Administration Guide for Solaris OS for the advantages and disadvantages of placing the Sybase ASE binaries on the local file system as opposed to the cluster file system.

• Sybase ASE configuration files – These files include the interfaces file, config file, and environment file. You can install these files on the local file system (with links), the highly available local file system, or on the cluster file system.

• Database data files – These files include Sybase device files. You must install these files on the highly available local file system or the cluster file system as either raw devices or regular files.

Installing the Sybase ASE 12.0 Software

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

• Prepare the nodes.

• Install the Sybase ASE software.

• Verify the Sybase ASE installation.

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.

How to Prepare the Nodes

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

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.

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 Software Installation Guide for Solaris OS for information on how to configure global devices.

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

Creating the Sybase ASE Database Environment

The procedures in this section enable you to complete the following tasks.

• Configure Sybase ASE database access with Solstice DiskSuite/Solaris Volume Manager or VxVM.

• Create the Sybase ASE database environment.

How to Configure Sybase ASE Database Access With Solstice DiskSuite/Solaris Volume Manager

If you use the Solstice DiskSuite/Solaris Volume Manager, perform the following steps to configure Sybase ASE database access with the Solstice DiskSuite/Solaris Volume Manager.

1. Configure the disk devices for the Solstice DiskSuite/Solaris Volume Manager software to use.

   See the Sun Cluster Software Installation Guide for Solaris OS for information on how to configure Solstice DiskSuite/Solaris Volume Manager.

2. If you use raw devices to contain the databases, run the following commands to change each raw-mirrored metadevice's owner, group, and mode.

   If you do not use raw devices, do not perform this step.

   1. If you create raw devices, run the following commands for each device on each node that can master the Sybase ASE resource group.

      # chown sybase /dev/md/metaset/rdsk/dn # chgrp dba /dev/md/metaset/rdsk/dn # chmod 600 /dev/md/metaset/rdsk/dn

      metaset

      Specifies the name of the diskset.

      /rdsk/dn

      Specifies the name of the raw disk device within the metaset diskset.

   2. Verify that the changes are effective.

      # ls -lL /dev/md/metaset/rdsk/dn

How to Configure Sybase ASE Database Access With VERITAS Volume Manager

If you use VxVM software, perform the following steps to configure Sybase ASE database access with the VxVM software.

1. Configure the disk devices for the VxVM software to use.

   See the Sun Cluster Software Installation Guide for Solaris OS for information on how to configure VERITAS Volume Manager.

2. If you use raw devices to contain the databases, run the following commands on the current disk-group primary to change each device's owner, group, and mode.

   If you do not use raw devices, do not perform this step.

   1. If you create raw devices, run the following command for each raw device.

      # vxedit -g diskgroup set user=sybase group=dba mode=0600 volume

      -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 nodes are considered as primary during failover.

   2. Verify that the changes are effective.

      # ls -lL /dev/vx/rdsk/diskgroup/volume

   3. Reregister the disk device group with the cluster to keep the VxVM namespace consistent throughout the cluster.

      # scconf -c -D name=diskgroup

How to Create the Sybase ASE Database Environment

Before you perform this procedure, ensure that you have completed the following tasks.

• Establish a highly available IP address and name, that is, a network resource that operates at installation time.

• Locate device paths for all of the Sybase ASE devices—including the master device and system devices—in the highly available local file system or cluster file system. Configure device paths as one of the following file types.

  • regular files

  • raw devices

  • files that the Solstice DiskSuite/Solaris Volume Manager software or the VxVM software manage

• Locate the Sybase ASE server logs in either the cluster file system or the local file system.

• The Sybase ASE 12.0 environment consists of the data server, backup server, monitor server, text server, and XP server. The data server is the only server that you must configure—you can choose whether to configure all of the other servers.

• The entire cluster must contain only one copy of the interfaces file. The $SYBASE directory contains the interfaces file. If you plan to maintain per-node file copies, ensure the file contents are identical.

  All of the clients that connect to Sybase ASE servers connect with Sybase OpenClient libraries and utilities. When you configure the Sybase ASE software, in the interfaces file, enter information about the network resource and various ports. All of the clients use this connection information to connect to the Sybase ASE servers.

Perform the following steps to create the Sybase ASE database environment.

1. Run the GUI-based utility srvbuild to create the Sybase ASE database.

   The $SYBASE/ASE_12-0/bin directory contains this utility. See the Sybase ASE document entitled Installing Sybase Adaptive Server Enterprise on Sun Solaris 2.x (SPARC).

2. To verify successful database installation, ensure that all of the servers start correctly.

   Run the ps(1) command to verify the operation of all of the servers. Sybase ASE server logs indicate any errors that have occurred.

3. Set the password for the Sybase ASE system administrator account.

   See the Sybase Adaptive Server Enterprise System Administration Guide for details on changing the sa login password.

4. Create a new Sybase ASE account for fault monitoring.

   This account enables the fault monitor to perform the following tasks.

   • Support queries to system tables.

   • Create and update user tables.

   ---

   Note –

   Do not use the sa account for these purposes.

   ---

   The following example shows how to create a new Sybase ASE account for fault monitoring.

   # isql -Usa -Psybase -Sasedb 1> use master 2> go 1> create database sc3xdb 2>go 1> sp_addlogin dbmon, dbmonp, sc3xdb 2> go 1> use sc3xdb 2> go 1> sp_changedbowner dbmon 2> go 1> sp_modifylogin dbmon, defdb, sc3xdb 2> go 1> exit

   See Sun Cluster HA for Sybase ASE Fault Monitor for more information.

5. Update the stop file with the sa password.

   Because the stop file contains the sa password, protect the file with the appropriate permissions, and place the file in a directory that the system administrator chooses. Enable only the sybase user to read, write, and execute the stop file.

   See Important Security Issues for more information about the stop file.

Where to Go From Here

After you create the Sybase ASE database environment, go to Installing the Sun Cluster HA for Sybase ASE Packages.

Installing the Sun Cluster HA for Sybase ASE Packages

If you did not install the Sun Cluster HA for Sybase ASE packages during your initial Sun Cluster installation, perform this procedure to install the packages. Perform this procedure on each cluster node where you are installing the Sun Cluster HA for Sybase ASE packages. To complete this procedure, you need the Sun Java Enterprise System Accessory CD Volume 3.

If you are installing more than one data service simultaneously, perform the procedure in “Installing the Software” in Sun Cluster Software Installation Guide for Solaris OS.

Install the Sun Cluster HA for Sybase ASE packages by using one of the following installation tools:

• The Web Start program

• The scinstall utility

The Web Start program is not available in releases earlier than Sun Cluster 3.1 Data Services 10/03.

How to Install the Sun Cluster HA for Sybase ASE Packages by Using the Web Start Program

You can run the Web Start program with a command-line interface (CLI) or with a graphical user interface (GUI). The content and sequence of instructions in the CLI and the GUI are similar. For more information about the Web Start program, see the installer(1M) man page.

1. On the cluster node where you are installing the Sun Cluster HA for Sybase ASE packages, become superuser.

2. (Optional) If you intend to run the Web Start program with a GUI, ensure that your DISPLAY environment variable is set.

3. Load the Sun Java Enterprise System Accessory CD Volume 3 into the CD-ROM drive.

   If the Volume Management daemon vold(1M) is running and configured to manage CD-ROM devices, it automatically mounts the CD-ROM on the /cdrom/cdrom0 directory.

4. Change to the Sun Cluster HA for Sybase ASE component directory of the CD-ROM.

   The Web Start program for the Sun Cluster HA for Sybase ASE data service resides in this directory.

   # cd /cdrom/cdrom0/\ components/SunCluster_HA_Sybase_3.1

5. Start the Web Start program.

   # ./installer

6. When you are prompted, select the type of installation.

   • To install only the C locale, select Typical.

   • To install other locales, select Custom.

7. Follow instructions on the screen to install the Sun Cluster HA for Sybase ASE packages on the node.

   After the installation is finished, the Web Start program provides an installation summary. This summary enables you to view logs that the Web Start program created during the installation. These logs are located in the /var/sadm/install/logs directory.

8. Exit the Web Start program.

9. Unload the Sun Java Enterprise System Accessory CD Volume 3 from the CD-ROM drive.

   1. To ensure that the CD-ROM is not being used, change to a directory that does not reside on the CD-ROM.

   2. Eject the CD-ROM.

      # eject cdrom

Where to Go From Here

Go to How to Register and Configure Sun Cluster HA for Sybase ASE.

How to Install Sun Cluster HA for Sybase ASE Packages by Using the scinstall Utility

1. Load the Sun Java Enterprise System Accessory CD Volume 3 into the CD-ROM drive.

2. Run the scinstall utility with no options.

   This step starts the scinstall utility in interactive mode.

   ---

   Note –

   Do not use the -s option of scinstall to specify a noniteractive installation of all data services.

   ---

3. Choose the menu option, Add Support for New Data Service to This Cluster Node.

   The scinstall utility prompts you for additional information.

4. Provide the path to the Sun Java Enterprise System Accessory CD Volume 3.

   The utility refers to the CD as the “data services cd.”

5. Specify the data service to install.

   The scinstall utility lists the data service that you selected and asks you to confirm your choice.

6. Exit the scinstall utility.

7. Unload the CD from the drive.

Where to Go From Here

Go to How to Register and Configure Sun Cluster HA for Sybase ASE.

Registering and Configuring Sun Cluster HA for Sybase ASE

Use the procedures in this section to register and configure the Sun Cluster HA for Sybase ASE data service. Register and configure Sun Cluster HA for Sybase ASE as a failover data service.

How to Register and Configure Sun Cluster HA for Sybase ASE

This procedure describes how to use the scrgadm(1M) command to register and configure Sun Cluster HA for Sybase ASE.

This procedure includes creating the SUNW.HAStoragePlus resource type. This resource type synchronizes actions between HAStorage and Sun Cluster HA for Sybase ASE and enables you to use a highly available local file system. Sun Cluster HA for Sybase ASE is disk-intensive, and therefore you should configure the SUNW.HAStoragePlus resource type.

See the SUNW.HAStoragePlus(1) man page and “Relationship Between Resource Groups and Disk Device Groups” in Sun Cluster Data Services Planning and Administration Guide for Solaris OS for more information about the SUNW.HAStoragePlus resource type.

Other options also enable you to register and configure the data service. See “Tools for Data Service Resource Administration” in Sun Cluster Data Services Planning and Administration Guide for Solaris OS for details about these options.

To perform this procedure, you must have the following information.

• The names of the cluster nodes that master the data service.

• The network resource that clients use to access the data service. You typically configure the IP address when you install the cluster. See the sections in the Sun Cluster Software Installation Guide for Solaris OS on planning the Sun Cluster environment and on how to install the Solaris operating environment for details.

• The path to the Sybase ASE application installation.

Perform the following steps on one cluster member.

1. Become superuser on a cluster member.

2. Run the scrgadm command to register resource types for Sun Cluster HA for Sybase ASE.

   # scrgadm -a -t SUNW.sybase

   -a

   Adds the resource type for the data service.

   -t SUNW.sybase

   Specifies the resource type name that is predefined for your data service.

3. Register the SUNW.HAStoragePlus resource type with the cluster.

   # scrgadm -a -t SUNW.HAStoragePlus

4. Create the resource sybase-hastp-rs of type SUNW.HAStoragePlus.

   # scrgadm -a -j sybase-hastp-rs -g sybase-rg -t SUNW.HAStoragePlus \ -x GlobalDevicePaths=sybase-device-group1,/dev/global/dsk/dl \ -x FilesystemMountPoints=/global/sybase-inst \ -x AffinityOn=TRUE

   ---

   Note –

   AffinityOn must be set to TRUE and the local file system must reside on global disk groups to be failover.

   ---

5. Run the scrgadm command to complete the following tasks and bring the resource group sybase-rg online on a cluster node.

   • Move the resource group into a managed state.

   • Bring the resource group online

   This node will be made the primary for device group sybase-set1 and raw device /dev/global/dsk/d1. Device groups associated with file systems such as /global/sybase-inst will also be made primaries on this node.

   # scrgadm -Z -g sybase-rg

6. Create Sybase ASE application resources in the failover resource group.

   # scrgadm -a -j resource -g resource-group \ -t SUNW.sybase \ -x Environment_File=environment-file-path \ -x Adaptive_Server_Name=adaptive-server-name \ -x Backup_Server_Name=backup-server-name \ -x Text_Server_Name=text-server-name \ -x Monitor_Server_Name=monitor-server-name \ -x Adaptive_Server_Log_File=log-file-path \ -x Stop_File=stop-file-path \ -x Connect_string=user/passwd -y resource_dependencies=storageplus-resource

   -j resource

   Specifies the resource name to add.

   -g resource-group

   Specifies the resource group name into which the RGM places the resources.

   -t SUNW.sybase

   Specifies the resource type to add.

   -x Environment_File=environment-file

   Sets the name of the environment file.

   -x Adaptive_Server_Name=adaptive-server-name

   Sets the name of the adaptive server.

   -x Backup_Server_Name=backup-server-name

   Sets the name of the backup server.

   -x Text_Server_Name=text-server-name

   Sets the name of the text server.

   -x Monitor_Server_Name=monitor-server-name

   Sets the name of the monitor server.

   -x Adaptive_Server_Log_File=log-file-path

   Sets the path to the log file for the adaptive server.

   -x Stop_File=stop-file-path

   Sets the path to the stop file.

   -x Connect_string=user/passwd

   Specifies the user name and password that the fault monitor uses to connect to the database.

   You do not have to specify extension properties that have default values. See Configuring Sun Cluster HA for Sybase ASE Extension Properties for more information.

7. Enable the resource and fault monitoring.

   ---

   Note –

   Sybase start logs print to the console when the Sybase servers start. If you do not want these messages to print to the console, update the appropriate RUN files to redirect these messages to another file.

   ---

   # scswitch -Z -g resource-group

Where to Go From Here

After you register and configure Sun Cluster HA for Sybase ASE, go to How to Verify the Sun Cluster HA for Sybase ASE Installation .

Verifying the Sun Cluster HA for Sybase ASE Installation

Perform the following verification tests to ensure that you have correctly installed and configured Sun Cluster HA for Sybase ASE.

These sanity checks ensure that all of the nodes that run Sun Cluster HA for Sybase ASE can start the Sybase ASE data server. These checks also ensure that other nodes in the configuration can access the Sybase ASE data server. Perform these sanity checks to isolate any problems with starting the Sybase ASE software from Sun Cluster HA for Sybase ASE.

How to Verify the Sun Cluster HA for Sybase ASE Installation

1. Log in to the node that masters the Sybase ASE resource group.

2. Set the Sybase ASE environment variables.

   The environment variables are the variables that you specify with the Environment_file extension property. See Table 1–2 for information on setting these environment variables.

3. Verify that the Sun Cluster HA for Sybase ASE resource is online.

   # scstat -g

4. Inspect the Sybase ASE logs to determine the cause of any errors that have occurred.

5. Confirm that you can connect to the data server and execute the following test command.

   # isql -S adaptive-server -U sa -P password isql> sp_help isql> go isql> quit

6. Kill the process for the Sybase ASE data server.

   The Sun Cluster software restarts the process.

7. Switch the resource group that contains the Sybase ASE resource to another cluster member.

   # scswitch -z -g resource-group -h node

8. Log in to the node that now contains the resource group.

9. Repeat Step 3 and Step 5.

   ---

   Note –

   Sybase ASE client connections cannot survive a Sun Cluster HA for Sybase ASE switchover. If a switchover occurs, the existing client connections to Sybase ASE terminate, and clients must reestablish their connections. After a switchover, the time that is required to replay the Sybase ASE transaction log determines Sun Cluster HA for Sybase ASE recovery time.

   ---

Location of Sun Cluster HA for Sybase ASE Log Files

Each instance of the Sun Cluster HA for Sybase ASE data service maintains log files in the /opt/SUNWscsyb/log directory.

These files contain information about actions that the Sun Cluster HA for Sybase ASE data service performs. Refer to these files to obtain diagnostic information for troubleshooting your configuration or to monitor the behavior of the Sun Cluster HA for Sybase ASE data service.

See also Sun Cluster HA for Sybase ASE Logging Issues.

Understanding Sun Cluster HA for Sybase ASE Logging and Security Issues

The following sections contain information about Sun Cluster HA for Sybase ASE logging and security issues.

Sun Cluster HA for Sybase ASE Logging Issues

Sun Cluster HA for Sybase ASE logs messages to the file message_log in the /opt/SUNWscsyb/log directory. Although this file cannot exceed 512 Kbytes, Sun Cluster HA for Sybase ASE does not delete old log files. The number of log files, therefore, can grow to a large number.

Sun Cluster HA for Sybase ASE writes all of the error messages in the syslog file. Sun Cluster HA for Sybase ASE also logs fault monitor history to the file restart_history in the log directory. These files can also grow to a large number.

As part of your regular file maintenance, check the following log files and remove files that you no longer need.

• syslog

• message_log

• restart_history

Important Security Issues

Sun Cluster HA for Sybase ASE requires that you embed the system administrator's password in a stop file. The /opt/SUNWscsyb/bin directory contains the template for the stop file, sybase_stop_servers. Sun Cluster HA for Sybase ASE uses this file to log in to the Sybase ASE environment and to stop the Sybase ASE servers. Enable the sybase user to execute the stop file, but protect the file from general access. Give read, write, and execute privileges to only the following users.

• sybase user

• sybase group

Configuring Sun Cluster HA for Sybase ASE Extension Properties

This section describes how to configure Sun Cluster HA for Sybase ASE extension properties. Typically, you use the command line scrgadm -x parameter=value to configure extension properties when you create the Sybase ASE resources. You can also use the procedures that “Administering Data Service Resources” in Sun Cluster Data Services Planning and Administration Guide for Solaris OS describes to configure them later.

See the r_properties(5) and the rg_properties(5) man pages for details on all of the Sun Cluster extension properties.

Table 1–2 describes the extension properties that you can set for the Sybase ASE server resource. You can update some extension properties dynamically. You can update others, however, only when you create or disable a resource. The Tunable entries indicate when you can update each property.

VARIABLE_NAME=VARIABLE_VALUE

Sun Cluster HA for Sybase ASE Fault Monitor

The Sun Cluster HA for Sybase ASE fault monitor queries the Sybase ASE server to determine server health.

The Sun Cluster HA for Sybase ASE fault monitor only monitors the Adaptive server. The fault monitor does not monitor auxiliary servers.

The fault monitor consists of the following processes.

• a main fault monitor process

• a database-client fault probe

The following sections describe the Sun Cluster HA for Sybase ASE fault monitor processes and the extension properties that the fault monitor uses.

Main Fault Monitor Process

The fault monitor process diagnoses errors and checks statistics. The monitor labels an operation successful if the following conditions occur.

• The database is online.

• The activity check returns no errors.

• The test transaction returns no errors.

If an operation fails, the main process checks the action table for an action to perform and then performs the predetermined action. If an operation fails, the main process can perform the following actions, which execute external programs as separate processes in the background.

1. Restarts the resource on the current node.

2. Restarts the resource group on the current node.

3. Fails over the resource group to the next node on the resource group's nodelist.

The server fault monitor also scans the Adaptive_Server_Log file and acts to correct any errors that the scan identifies.

Database-Client Fault Probe

The database-client fault probe performs activity checks and test transactions. The extension property Connect_string specifies an account that performs all of the database operations. The extension property Probe_timeout sets the time-out value that the probe uses to determine the time that has elapsed in a successful database probe.

Extension Properties

The fault monitor uses the following extension properties.

• Thorough_probe_interval

• Retry_count

• Retry_interval

• Probe_timeout

• Connect_string

• Connect_cycle

• Adaptive_Server_Log

See Configuring Sun Cluster HA for Sybase ASE Extension Properties for more information about these extension properties.