HP Serviceguard Enterprise Cluster Master Toolkit User Guide (5900-2145, April 2013)

Table 7 Sybase ASE attributes (continued)
DescriptionSybase ASE Attributes
The interval of time, in seconds, which this script should wait between checks to ensure
that Sybase database is running. Default value is 30 seconds.
MONITOR_INTERVAL
The interval of time, in seconds, to wait for Sybase abort to complete before killing the
Sybase processes defined in MONITOR_PROCESSES. The TIME_OUT variable is used
TIME_OUT
to protect against a worst case scenario where a hung database prevents the halt script
from completing, therefore preventing the standby node from starting the database. The
value of TIME_OUT must be less than the time-out set in the package configuration file.
TIME_OUT variable has no effect on package failover times. Default value is 30 seconds.
The maximum amount of time in seconds to wait for an ASE to complete recovery before
determining that the server has failed to start up. This value must be set to allow enough
time for all the databases to recover and come online.
RECOVERY_TIMEOUT
The names of all processes that must be executing to ensure this instance is up and
running.
MONITOR_PROCESSES
Maintenance flag enables or disables the maintenance mode for the Sybase package.
By default this is set to "yes". To enable this feature, MAINTENANCE_FLAG must be set
MAINTENANCE_FLAG
to "no". If the Sybase ASE instance must be maintained, a file $TKIT_DIR/
sybase.debug must be created. During this maintenance period monitoring of the
Sybase ASE instance is paused. Even if the ASE instance is brought down, the package
is not failed over to the standby node. To continue monitoring and come back from the
maintenance mode, the sybase.debug file must be removed. You must ensure that
the ASE instance is running properly after the maintenance phase.
• Module Script (tkit_module.sh)
This script contains a list of internally used variables and functions that support the starting
and stopping of an Sybase ASE database instance. This script is called by the Master Control
Script to perform the following:
1. On package start-up, it starts the Sybase ASE instance and launches the monitor process.
2. On package halt, it stops the Sybase ASE instance and monitor process.
This script also contains the functions for monitoring the Sybase ASE instance. By default,
only the "dataserver" process of ASE is monitored. This process is contained in the variable
MONITOR_PROCESSES.
Sybase Package Configuration Example
Package Setup and Configuration
When Sybase ASE is already installed in the default home directory (for example, /home/sybase),
perform the following steps to make necessary directories shareable by all clustered nodes.
For more information on how to create a logical volume infrastructure on a shared disk, see Building
an HA Cluster Configuration in the latest Managing Serviceguard manual available at http://
www.hp.com/go/hpux-serviceguard-docs—>HP Serviceguard manual .
The disk must be available to all clustered nodes that are configured to run this database instance.
Create a file system to hold the necessary configuration information and symbolic links to the
Sybase ASE executables. This file system will be used as SYBASE_HOME in the package control
scripts. The volume group and file system must be uniquely named within the cluster, therefore, use
the name of the database instance ($ASE_SERVER) in the name. Consider that the name of the
database is 'SYBASE0', follow the instructions in the section Building an HA Cluster Configuration
in the latest Managing Serviceguard manual to create the following:
/dev/vg0_SYBASE0 (the volume group)
/dev/vg0_SYBASE0/lvol1 (the logical volume)
/dev/vg0_SYBASE0/lvol1 (the filesystem) mounted at /SYBASE0
68 Using the Sybase ASE Toolkit in a Serviceguard Cluster on HP-UX