HP Serviceguard Oracle DataGuard Toolkit User Guide, April 2011

Single-instance environment
NOTE: The example assumes that the package name is dgpkg, and the package directory is
/etc/cmcluster/pkg/dgpkg, and the ORACLE_HOME is configured as /orahome.
1. Disable the failover of the package 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 ODG process daemons’ processes, would now stop monitoring these
processes. The message, “Serviceguard Toolkit for ODG pausing Data Guard monitoring and
entering maintenance mode” appears in the Serviceguard Package log file.
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: Database maintenance).
5. Restart the Oracle database instance again if you manually stopped it prior to maintenance.
$ cd /etc/cmcluster/pkg/dgpkg/
$ $PWD/hadg.sh start
6. Allow monitoring scripts to continue normally as shown below:
$ rm -f /etc/cmcluster/pkg/dgpkg/dataguard.debug
The message “Starting ODG monitoring again after maintenance” appears in the Serviceguard
Package Control script log.
7. Enable the package failover
$ cmmodpkg -e dgpkg
RAC environment
The ODG package in an RAC Environment can be put into maintenance mode the same way it is
done in a single-instance Environment. However, it is to be noted that, if the CRS package goes
into maintenance mode, then SGeRAC DB toolkit module (which is dependant on the CRS package)
also goes into maintenance and hence stops monitoring the database. But the ODG toolkit module
does not go into maintenance mode automatically. The user has to manually put it in maintenance
mode.
NOTE: If a package failure occurs during maintenance operations, the package does not
automatically failover to an adoptive node. You must manually start the package on the adoptive
node. For more information on manually starting the package on an adoptive node, see the
“Managing HP Serviceguard” guide available at http://www.hp.com/go/hpux-serviceguard-docs
Oracle Data Guard maintenance 33