HP Serviceguard Enterprise Cluster Master Toolkit User Guide, June 2014

By default, Local OS Authentication is enabled for Oracle 10g and 11g with default value of
"LOCAL_OS_AUTHENTICATION_listener_name = ON". The absence of this parameter in
LISTENER.ORA file implies the feature is enabled. If this feature is disabled, it can be re-enabled
by commenting or removing "LOCAL_OS_AUTHENTICATION_listener_name = OFF" from
LISTENER.ORA or by setting it to "LOCAL_OS_AUTHENTICATION_listener_name = ON".
NOTE: Plain text listener passwords cannot contain any space between characters when used
with Oracle toolkit.
Database Maintenance
There might be situations, when the Oracle database must be shut down for maintenance purposes
like changing configuration, without migrating the instance to standby node.
NOTE: This feature is enabled only when the package attribute MAINTENANCE_FLAG is set to
"yes".
For this example, consider that the package name is ORACLE_TEST0, package directory is
/etc/cmcluster/pkg/ORACLE_TEST0 and the ORACLE_HOME is configured as /ORACLE_TEST0.
Follow the procedure for the Database Maintenance:
1. Disable the failover of the package through cmmodpkg command:
$ cmmodpkg -d ORACLE_TEST0
2. Pause the monitor script.
Create an empty file /etc/cmcluster/pkg/ORACLE_TEST0/oracle.debug:
$ touch /etc/cmcluster/pkg/ORACLE_TEST0/oracle.debug
Toolkit monitor scripts (both database instance and listener monitoring scripts) which
continuously monitor Oracle process daemons' processes and the listener process, stops
monitoring these daemon processes. The following messages appear in the Serviceguard
Package Control script log: "Oracle toolkit pausing monitoring and entering maintenance
mode" and "Oracle toolkit pausing Listener <Listener_Name> monitoring and entering
maintenance mode".
3. If required, stop the Oracle database instance:
$ cd /etc/cmcluster/pkg/ORACLE_TEST0/
$ $PWD/toolkit.sh stop
4. Perform maintenance actions (for 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 before maintenance:
$ cd /etc/cmcluster/pkg/ORACLE_TEST0/
$ $PWD/toolkit.sh start
6. Allow monitoring scripts to continue normally:
$ rm -f /etc/cmcluster/pkg/ORACLE_TEST0/oracle.debug
The following messages "Starting Oracle toolkit monitoring again after maintenance" and
"Starting Oracle Listener monitoring again after maintenance" appear in the Serviceguard
Package Control script log.
7. Enable the package failover
$ cmmodpkg -e ORACLE_TEST0
56 Using the Oracle Toolkit in an HP Serviceguard Cluster