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

package configuration file). This can be done at the time of
configuring
the ASE server processes, with entries made in the <ASE_SERVER.cfg>
file
while configuring with the default configuration tool, or in
the
$SYBASE/$SYBASE_ASE/init/sample_resource_files/srvbuild.adaptive_server.r
s
and similarly for the other servers.
NOTE: The dataserver and the monitor server, both need to be
installed
on the same disk as monitor server is dependent on the presence of
the
dataserver for its working.
b. Make sure that the 'sybase' user has the same user id and group id
on
all nodes in the cluster. Create the user/group with the
following
commands and ensure the uid/gid by editing the /etc/passwd file.
# groupadd sybase
# useradd -g sybase -d <installpath> -p <Passwd> sybase
c. Create a volume group, logical volume and file system to
hold
the necessary configuration information and symbolic links to the
Sybase
ASE executables. This file system will be defined as SYBASE in
the
package configuration file and master control script. Since the
volume
group and file system must be uniquely named within the cluster, use
the
name of the database instance (ASE_SERVER) in the names:
Assuming that the name of the ASE instance is 'SYBASE0', create
the
following:
A volume group: /dev/vg0_SYBASE0
A logical volume: /dev/vg0_SYBASE0/lvol1
A file system: /dev/vg0_SYBASE0/lvol1 mounted at /SYBASE0
After the volume group, logical volume and file system have
been
created on one node, it must be imported to the other nodes
that
will run this database. Create the directory /SYBASE0 on
all
nodes so that /dev/vg0_SYBASE0/lvol1 can be mounted on that
node
if the package is to be run on the node.