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

• 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

"modular1.ascii" now 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

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.

Leave the value of ASM to the default value “no". The new toolkit parameters can be left

as they are by default.

• Apply the new modular package configuration using cmapplyconf.

• Start the database package.

4. Migration to a modular database package using ASM:

• Halt the database package.

• 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.

• Configure a modular ASM MNP as mentioned in this document.

• Apply the ASM MNP configuration.

• Run the ASM MNP.

• For 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>

Modifying a legacy database package using an older version of Oracle ECMT scripts to use the scripts provided for ASM

support