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

7) Apply the package configuration.
# cmapplyconf -P db1pkg.conf
This command applies the package configuration to the cluster It also creates the
toolkit configuration directory defined by the package attribute TKIT_DIR on all target
nodes, if it is not already present, and then creates the toolkit configuration file in it
with the values specified in the db1pkg.conf file.
8) Open the haoracle.conf file generated in the package directory (TKIT_DIR ) .
Ensure the attribute ORA_CRS_HOME is set to the Oracle Clusterware Home directory
and the attribute OC_TKIT_DIR is set to the SGeRAC OC MNP package directory.
9) For a running database package, if the value of any of the package attributes need
to be modified, then the package needs to be restarted. The given below steps should
be followed to update the attribute values of a running database packages :
a) Edit the package configuration file and populate the new values.
b) Halt the package
c) Apply the package configuration file.
d) Start the package
Modifying a legacy database package using an older version of Oracle
ECMT scripts to use the scripts provided for ASM support
A customer can migrate from an older ECMT version database package to use the Oracle ECMT
scripts provided for ASM support. The new legacy or modular database package may or may not
use ASM.
1. Migration to a legacy database package not using ASM:
• Halt the database package.
• Copy the framework scripts provided in the bundle to the package directory on one node.
• Edit the configuration file haoracle.conf in the package directory. Leave the
INSTANCE_TYPE to the default value "database". Configure values for all parameters
that were present in the older toolkit configuration file, that is, ORACLE_HOME,
ORACLE_ADMIN, SID_NAME, LISTENER, LISTENER_NAME,
LISTENER_PASSWORD, PFILE, MONITORED_PROCESSES, MAINTENANCE_FLAG,
MONITOR_INTERVAL, TIME_OUT. Leave the value of ASM to the default value "no".
The new parameters can be left as they are by default.
• Copy all the scripts from the package directory from this node to all the configured nodes.
• Start the database package. There is no need to re-apply the package configuration since
no changes are being made to the package ASCII file.
2. Migration to a legacy database package using ASM:
• Halt the database package.
• Configure ASM on all the configured nodes as mentioned in this document. Create ASM
disk groups, configure the raw logical volumes and make the database instance use the
ASM storage. Steps to migrate a database to ASM can be found in Oracle manuals.
• Configure an ASM MNP as mentioned in this document.
• Apply the ASM MNP configuration.
• Run the ASM MNP.
• Copy the framework scripts provided in the bundle to the database instance package
directory.
• Configure the configuration file haoracle.conf file as mentioned in this document for the
database package.
48 Using the Oracle Toolkit in an HP Serviceguard Cluster