HP Enterprise Cluster Master Toolkit User Guide (5900-2131, December 2011)

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. In case if it has been 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 white spaces ( " " ) when used with Oracle
toolkit.
Database Maintenance
There might be situations, when the Oracle 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 followed:
NOTE: This feature is enabled only when the package attribute MAINTENANCE_FLAG is set to
"yes".
The example assumes that the package name is ORACLE_TEST0, package directory is
/etc/cmcluster/pkg/ORACLE_TEST0 and the ORACLE_HOME is configured as /ORACLE_TEST0.
• Disable the failover of the package through cmmodpkg command:
$ cmmodpkg -d ORACLE_TEST0
• Pause the monitor script.
Create an empty file /etc/cmcluster/pkg/ORACLE_TEST0/oracle.debug as shown below:
$ 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, would now
stop monitoring these daemon processes. Two messages, "Oracle toolkit pausing monitoring
and entering maintenance mode" and "Oracle toolkit pausing Listener <Listener_Name>
monitoring and entering maintenance mode" appears in the Serviceguard Package Control
script log.
• If required, stop the Oracle database instance as shown below:
$ cd /etc/cmcluster/pkg/ORACLE_TEST0/
$ $PWD/toolkit.sh stop
• 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).
• Re-start the Oracle database instance again if you manually stopped it prior to maintenance
$ cd /etc/cmcluster/pkg/ORACLE_TEST0/
$ $PWD/toolkit.sh start
• Allow monitoring scripts to continue normally as shown below:
$ rm -f /etc/cmcluster/pkg/ORACLE_TEST0/oracle.debug
Two messages "Starting Oracle toolkit monitoring again after maintenance" and "Starting
Oracle Listener monitoring again after maintenance" appear in the Serviceguard Package
Control script log.
• Enable the package failover
$ cmmodpkg -e ORACLE_TEST0
52 Using the Oracle Toolkit in an HP Serviceguard Cluster