Using the Sybase ASE Toolkit in a Serviceguard Cluster on HP-UX README: Release B.06.00

instance. By default, only the "€˜dataserver€" process of ASE is
monitored.
This process is contained in the variable MONITOR_PROCESSES.
E. Sybase Package Configuration Example
- Package Setup and Configuration
1. Assuming Sybase ASE is already installed in its default
home
directory (e.g., /home/sybase), perform the following steps to
make
necessary directories shareable by all clustered nodes.
Follow the instructions in the chapter "Building an HA
Cluster
Configuration" in the "Managing Serviceguard" manual to create a
logical volume infrastructure on a shared disk.The disk must be
available
to all clustered nodes that will be 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.
Since
the volume group and file system have to be uniquely named within
the
cluster, use the name of the database instance ($ASE_SERVER) in the
name.
Assuming the name of the database is '€˜SYBASE0', follow the
instructions
in the "Managing Serviceguard" manual ("Building an HA Cluster
Configuration") 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
2. Assuming Sybase ASE is installed in /home/sybase; create
symbolic
links to all subdirectories under /home/sybase with the exception of
the
dbs directory (dbs contains important instance configuration files,
and
should reside in the shared storage in ${ASE_SERVER},
e.g.,
/SYBASE0/dbs).
3. Test the set up to ensure Sybase ASE can be properly brought up.
Repeat this step on all other clustered nodes to be configured to run
the