The 'ORACLE_TEST0' instance should now be reachable using the name 'ORACLE_TEST0' regardless of the node on which it is running.

Listener:

Set up a listener process for each Oracle instance that executes on a Serviceguard cluster, making sure that the listener can move with the instance to another node. Effectively, ensure the listener configured to a specific Oracle instance is assigned to a unique port.

In the current release you can configure ONE listener to be monitored by the toolkit.

However you can configure multiple listeners for the Oracle instance outside the Serviceguard environment to provide more HA to the listener.

NOTE: It is recommended to use encrypted passwords for password protected listeners.

The password specified for a listener in the parameter PASSWORDS_<listener_name> in the file LISTENER.ORA, must be copied to the LISTENER_PASS parameter in the haoracle.conf file. If there are multiple passwords configured for a single listener, you can use any one of them for the LISTENER_PASS parameter in the haoracle.conf.

In particular, for Oracle 10g and 11g, there is a new listener feature called "Local OS Authentication" activated by default, which permits the user who started it to administer the listener without requiring password authentication. To disable this feature, you need to specify "LOCAL_OS_AUTHENTICATION_listener_name = OFF" in LISTENER.ORA. Please note, in this situation, due to a change in Oracle 10g, you will have to specify the plain text password for the LISTENER_PASS parameter in haoracle.conf (and not the encrypted password found in LISTENER.ORA).

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>

Database Maintenance

51