Using the Serviceguard Toolkit for Oracle Data Guard in an HP Serviceguard Cluster B.01.00, September 2010

There might be situations, when the Oracle Data guard database instances
have to be
taken down for maintenance purposes like changing configuration, without
having the
instance to migrate to standby node. The following procedure should be
followed:
The maintenance feature is enabled only when the configuration variable
MAINTENANCE_FLAG is
set to "yes" in the toolkit configuration file.
Note: The example assumes that the package name is dgpkg, package
directory is
/etc/cmcluster/pkg/dgpkg and the ORACLE_HOME is configured as /orahome.
1. Disable the package switching through cmmodpkg command.
$ cmmodpkg -d dgpkg
2. Pause the monitor script
Create an empty file /etc/cmcluster/pkg/dgpkg/dataguard.debug as
shown below:
$ touch /etc/cmcluster/pkg/dgpkg/dataguard.debug
Toolkit monitor scripts (both database instance and listener monitoring
scripts) which
continuously monitor Oracle Data Guard process daemons' processes, would
now
stop monitoring these daemon processes. The messages, "Serviceguard
Toolkit for Oracle Data
Guard pausing Dataguard monitoring and entering maintenance mode" appears
in the Serviceguard
Package Control script log.
3. If required, stop the database instance(s) as shown below:
$ cd /etc/cmcluster/pkg/dgpkg/
$ $PWD/hadg.sh stop
4. Perform maintenance actions (Example: changing the configuration
parameters in
the parameter file of the Oracle instance. If this file is changed,
please remember to
distribute the new file to all cluster nodes).
5. Re-start the Oracle database instance again if you manually stopped
it prior to
maintenance
$ cd /etc/cmcluster/pkg/dgpkg/
$ $PWD/hadg.sh start