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

maintained across the nodes. A disadvantage of storing
the
configuration on local disks is that this can increase the chance
of
the configuration for a database instance becoming inconsistent
if
changes are made to the configuration in one node, and
this
configuration data is not distributed to all nodes that can run
that
database instance.
It is therefore recommended that the master database and other
ASE
system database files - like master.dat, sysprocs.dat and
sybsysdb.dat
- be on shared disk.
The user is adviced to get the appropriate license for this type
of
setup. In case of license that is server specific, each node
will
require a license to be generated with the corresponding MAC of
that
node. In case of local configuration, the license for each node can
be
separately put on the corresponding node under
the
$SYBASE/$SYBASE_SYSAM2/licenses directory. In case of a
shared
configuration, please ensure that both nodes can access
the
corresponding license in the same path.
However, in case of local configuration, please note that the
Sybase
ASE instance specific files MUST be identical on all nodes; and in
the
case of shared configuration, all files must be on shared storage
and
be accessible from any one node at any given time.)
C. Setting up the Application
NOTE: This README assumes that Sybase ASE has already been
installed
in /home/Sybase ASE on all nodes in the cluster, and that
shared
storage has been configured.
a. Make sure all database instances in the cluster have
unique
names (as identified by the user-defined variable 'ASE_SERVER' in
the