Using the Oracle Toolkit in a HP Serviceguard Cluster README Revision: B.06.00, August 2010

- To add the values to this modular package configuration file, from
the
older toolkit configuration file, issue the following command:
# cmmakepkg -i modular.ascii -m ecmt/oracle/oracle -t <older
toolkit
configuration file> modular1.ascii
- "modular1.ascii" now has values for certain attributes which were
present
in the older toolkit configuration file. Parameters like
ORACLE_HOME,
ORACLE_ADMIN, SID_NAME, PFILE, LISTENER, LISTENER_NAME,
LISTENER_PASS,
MONITOR_PROCESSES, MAINTENANCE_FLAG, MONITOR_INTERVAL and TIME_OUT
will
have values from the old toolkit configuration file. They can be
edited if
needed for the new environment. Edit the value for TKIT_DIR (where
the new
toolkit configuration file should be generated or where the toolkit
scripts are copied to in case of a configuration directory mode of
operation). Leave the INSTANCE_TYPE to the default value
"database". Edit
the parameters ASM, ASM_DISKGROUP, ASM_VOLUME_GROUP, ASM_HOME,
ASM_USER,
ASM_SID, KILL_ASM_FOREGROUNDS, CLEANUP_BEFORE_STARTUP and
USER_SHUTDOWN_MODE
as mentioned for the database package.
- Apply the new modular package configuration using cmapplyconf.
- Start the database package.
F. Adding the Package to the Cluster
After the setup is complete, add the package to the Serviceguard
cluster and start it.
$ cmapplyconf -P ORACLE_TEST0
$ cmmodpkg -e -n <node1> -n <node2> ORACLE_TEST0
$ cmmodpkg -e ORACLE_TEST0
If necessary, consult the manual "Managing Serviceguard" for
information on managing packages.
G. Node-specific Configuration
On many clusters, the standby nodes might be lower end systems than
the
primary node. An SMP machine might be backed up by a uniprocessor,
or a machine with a large main memory may be backed up by a node with