HP Serviceguard Enterprise Cluster Master Toolkit User Guide, December 2012 (5900-2145)

$ export SG_PACKAGE=SYBASE0
$ $SGCONF/scripts/ecmt/sybase/tkit_module.sh stop
4. Perform maintenance actions (for example, change the configuration parameters in the
parameter file of the Sybase ASE instance. If this file is changed, distribute the new file to all
cluster nodes).
5. Start the Sybase ASE database instance again if it is stopped:
$ export SG_PACKAGE=SYBASE0
$ SGCONF/scripts/ecmt/sybase/tkit_module.sh start
6. Allow monitoring scripts to continue normally:
$ rm -f /opt/cmcluster/pkg/SYBASE0/sybase.debug
A message "Starting Sybase ASE toolkit monitoring again after maintenance" appears in the
Serviceguard Package Control script log.
7. Enable the package failover:
$ cmmodpkg -e SYBASE0
NOTE:
• If the package fails during maintenance (for example, the node crashes), the package
does not automatically fail over to an adoptive node. You must startup the package on
an adoptive node. For more information, see theManaging Serviceguard manual available
at http://www.hp.com/go/hpux-serviceguard-docs —>HP Serviceguard
This feature is enabled only when the configuration variable MAINTENANCE_FLAG is set
to "yes" in the package configuration file.
• HP suggests you to have different toolkit directories for each package. If two or more
packages share the same toolkit directory and if one package enters the maintenance
mode, it will affect the other package too.
Cluster Verification for Sybase ASE Toolkit
Cluster verification is a proactive mechanism to identify cluster inconsistencies that adversely affects
toolkit package failover to a node. This mechanism checks for Serviceguard, ECMT, and Sybase
ASE versions on all the package nodes of the cluster. If there are any inconsistencies, it does not
fail the cmcheckconf command, but logs appropriate warning messages.
Example:
Consider a two-node cluster, where both nodes have Serviceguard A.11.20, and ECMT B.07.00.01,
but different versions of Syabse ASE.
To check the package configuration, run the cmcheckconf command.
For example: node1# cmcheckconf -P pkg.conf
On node1, validation of the package Sybase_pkg, succeeded with:
The toolkit configuration file will be backed up and a new file will be created in tkit_dir when the package
configuration is applied.
On node2, validation of package Sybase_pkg succeeded with:
The toolkit configuration file will be backed up and a new file will be created in tkit_dir when the package
configuration is applied.
WARNING: Sybase ASE version on all package nodes does not match.
Check syslog for more details.
cmcheckconf: Verification completed. No errors found.
Use the cmapplyconf command to apply the configuration.
Cluster Verification for Sybase ASE Toolkit 73