User's Manual

• 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.
• Create a new package ASCII file and control script or edit the existing package ASCII
and control scripts in the database package directory. Configure the parameters as
mentioned for the database package.
• Copy the scripts from the package directory to all the configured nodes.
• Remove the older database package configuration if a new package for the database
instance is being configured.
• Apply the database package configuration.
• Run the database package.
3. Migration to a modular database package not using ASM:
• Halt the database package.
• In case of configuration directory mode of operation to be used, copy the new Oracle
scripts to another package directory.
• Migrate the older legacy package to a modular package containing Serviceguard
parameters.
# cmmigratepkg -p <legacy_pkg_name> -s -o <modular_pkg_name>
Refer to the Whitepaper "Migrating Packages from Legacy to Modular Style, October
2007" and also the Whitepaper Modular package support in Serviceguard for Linux
and ECM Toolkits available at http://www.hp.com/go/hpux-serviceguard-docs —>HP
Serviceguard Enterprise Cluster Master Toolkit
• 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
48 Using the Oracle Toolkit in an HP Serviceguard Cluster