HP Serviceguard Linux Oracle-Toolkit-A.05.01.00 User Guide (696983-001, June 2012)

5 Migrating a database package
You can migrate from an existing database package that uses the older version of HP Serviceguard
toolkit for Oracle to use the new Linux HP Serviceguard toolkit for Oracle scripts provided for ASM
support. The new legacy or modular database package may or may not use ASM.
Migrating legacy Oracle database package without ASM to modular
To migrate a legacy Oracle database package without ASM to modular Oracle database package
without ASM:
1. Halt the database package.
2. Copy the new Oracle scripts to another package directory if you are using the configuration
directory mode of operation.
3. Migrate the older legacy package to a modular package containing Serviceguard parameters
using the following command:
# cmmigratepkg -p <legacy_pkg_name> -s -o <modular1.ascii>
4. Add the values to the modular package configuration file, from the older toolkit configuration
file using the following command:
# cmmakepkg -i modular.ascii -m tkit/oracle/oracle -t <older toolkit
configuration file> modular1.ascii
5. Edit the value for TKIT_DIR where the new toolkit configuration file is generated or where
the toolkit scripts are copied to, in case of a configuration directory mode of operation.
6. Apply the new modular package configuration using the cmapplyconf command.
7. Start the database package.
Migrating legacy ASM database package to modular
To migrate legacy ASM database package to modular ASM database package:
1. Halt the database package.
2. Configure ASM on all the configured nodes.
3. Create ASM disk groups, configure the raw logical volumes, and make the database instance
use the ASM storage.
4. Configure a modular ASM MNP.
5. Apply the ASM MNP configuration.
6. Run the ASM MNP.
7. For the database package, in the case of configuration directory mode of operation, copy
the new Oracle scripts to another package directory.
8. Migrate the older legacy package to a modular package containing Serviceguard parameters,
using the following command:
# cmmigratepkg -p <legacy_pkg_name> -s -o <modular_pkg_name>
9. Add the values to the modular package configuration file, from the older toolkit configuration
file using the following command:
# cmmakepkg -i modular.ascii -m tkit/oracle/oracle -t <older toolkit
configuration file> modular1.ascii
10. Edit the value for TKIT_DIR where the new toolkit configuration file is generated or where
the toolkit scripts are copied to, in the case of a configuration directory mode of operation.
11. Apply the new modular package configuration using the cmapplyconf command.
12. Start the database package.
42 Migrating a database package