HP Serviceguard Toolkit for Oracle Version A.05.01.01 on Linux User Guide (December, 2012)

8. Edit the package control script db1pkg.cntl.
ExampleAttribute Name
"oracle_service"SERVICE_NAME[0]
"$SGCONF/oracle_legacy/toolkit.sh
monitor"
SERVICE_CMD[0]
""SERVICE_RESTART[0]
If LISTENER parameter has been set to yes in the package configuration file haoracle.conf
then initialize the following parameters:
ExampleAttribute Name
"oracle_listener_service"SERVICE_NAME[1]
"$SGCONF/oracle_legacy/toolkit.sh
monitor_listener"
SERVICE_CMD[1]
""SERVICE_RESTART[1]
If service is configured for database hang detection in the package configuration file, set the
following parameters:
ExampleAttribute Name
"oracle_hang_service"SERVICE_NAME[2]
"$SGCONF/oracle_legacy/toolkit.sh
hang_monitor 30 failure"
SERVICE_CMD[2]
""SERVICE_RESTART[2]
9. Distribute the package configuration file, package control script, and the toolkit scripts to all
the nodes.scp $SGCONF/oracle_legacy/* root
@<hostname>:$SGCONF/oracle_legacy/
10. Apply the package configuration using the following command:
# cmapplyconf -P db1pkg.conf
11. Repeat all the above mentioned steps for each database instance.
Stop the Oracle database instance if it is running.
12. Run the database package using the following command:
# cmrunpkg oracle_legacy
Configuring modular Oracle database package without ASM
To configure a modular Oracle database toolkit packages without ASM:
1. Create a directory in $SGCONF/<package dir>. For example:
#mkdir $SGCONF/oracle_pkg
2. cd $SGCONF/<oracle_pkg>.
3. Create the modular package configuration file, pkg2.conf using the command:
# cmmakepkg -m tkit/oracle/oracle pkg2.conf
4. Edit the modular package configuration file pkg2.conf. Table 3 (page 18) describes the list
of attributes that you can edit.
Configuring legacy and modular Oracle ASM instance and Database instance toolkit packages 17