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

the ASE instance, the /etc/hosts file on each node
should
contain the re-locatable IP-address associated with the
physical
hostname of that node. For example, if node1_hostname
and
node2_hostname are the physical hostnames of two nodes in
the
cluster, and if 192.168.10.1 is the re-locatable IP-address
for
the ASE instance, then the /etc/hosts of node1 should have
an
entry like:
192.168.10.1 node1_hostname
And the /etc/hosts file of node2 should have an entry like:
192.168.10.1 node2_hostname.
K. Database Maintenance
There might be situations, when the Sybase ASE database has to be
taken
down for maintenance purposes like changing configuration, without
having
the instance to migrate to standby node. The following procedure
should
be used:
Note: The example assumes that the package name is SYBASE0,
package
directory is /opt/cmcluster/pkg/SYBASE0 and the SYBASE_HOME is
configured as /SYBASE0.
- Disable the failover of the package through cmmodpkg command.
$ cmmodpkg -d SYBASE0
- Pause the monitor script
Create an empty file <TKIT_DIR>/sybase.debug as shown below:
$ touch <TKIT_DIR>/sybase.debug
Toolkit monitors script that continuously monitors Sybase ASE
process,
would now stop monitoring this process. A message, "Sybase ASE
toolkit
pausing monitoring and entering maintenance mode" appears in
the
Serviceguard Package Control script log.
- If required, stop the Sybase ASE database instance as shown below:
$ export SG_PACKAGE=SYBASE0
$ $SGCONF/scripts/ecmt/sybase/tkit_module.sh stop