HP Serviceguard Enterprise Cluster Master Toolkit User Guide, December 2012 (5900-2145)

6. Copy the framework scripts provided in the bundle to the database instance package directory.
7. Configure the configuration file haoracle.conf file as mentioned in this document for the
database package.
8. Do one of the following:
• Create a new package ASCII file and control script.
• Edit the existing package ASCII and control scripts in the database package directory.
• Configure the parameters as mentioned for the database package.
9. Copy the scripts from the package directory to all the configured nodes.
10. Remove the older database package configuration if a new package for the database instance
is being configured.
11. Apply the database package configuration.
12. Run the database package.
Migration to a modular database package not using ASM:
1. Halt the database package.
2. To use configuration directory mode of operation, copy the new Oracle scripts to another
package directory.
3. Migrate the older legacy package to a modular package containing Serviceguard parameters.
4. # cmmigratepkg -p <legacy_pkg_name> -s -o <modular_pkg_name>
For more information, see 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
5. 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
Now, "modular1.ascii" has values for certain attributes that were present in the older toolkit
configuration file. Edit the value for TKIT_DIR (where the new toolkit configuration file must
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. Leave the value
of ASM to the default value “no". By default, the value for the new toolkit parameters is
retained.
6. Apply the new modular package configuration using cmapplyconf.
7. Start the database package.
Migration to a modular database package using ASM:
1. Halt the database package.
2. Configure ASM on all 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.
3. Configure a modular ASM MNP as mentioned in this document.
4. Apply the ASM MNP configuration.
5. Run the ASM MNP.
6. To use configuration directory mode of operation for the database package, (Please check
the technical accuracy).
7. Migrate the older legacy package to a modular package containing Serviceguard parameters.
# cmmigratepkg -p <legacy_pkg_name> -s -o <modular_pkg_name>
52 Using the Oracle Toolkit in an HP Serviceguard Cluster