Using the Oracle Toolkit in a HP Serviceguard Cluster README Revision: B.06.00, August 2010

E. Modification of a legacy database package using 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, i.e. 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.