HP Serviceguard Toolkit for Oracle on Linux User Guide (May 2013)

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. Add $SGCONF/oracle_legacy/toolkit.sh start command in the
customer_defined_run_cmds function. You must add this command before the
test_return 51 command.
10. Add ${SGCONF}/oracle_legacy/toolkit.sh stop $reason command in the
customer_defined_halt_cmds function.
You must add this line before the test_return 52 command.
11. 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/
12. Apply the package configuration using the following command:
# cmapplyconf -P db1pkg.conf
13. Repeat all the above mentioned steps for each database instance.
Stop the Oracle database instance if it is running.
14. Run the database package using the following command:
# cmrunpkg oracle_legacy
For additional information about customer_defined run and halt commands, see “Sample
package configuration file for Oracle database legacy package without ASM” (page 61)
Configuring modular Oracle database package without ASM
To configure a modular Oracle database toolkit packages without ASM:
Configuring legacy and modular Oracle ASM instance and Database instance toolkit packages 17