service_restart none
service_fail_fast_enabled no service_halt_timeout 300 service_name Oracle_listener_service
service_cmd "$SGCONF/scripts/ecmt/Oracle/tkit_module.sh Oracle_monitor_listener" service_restart none
service_fail_fast_enabled no service_halt_timeout 300
If the listener is not configured, comment the second set of service parameters which are used to monitor the listener.
Edit the dependency parameters as shown:
dependency_name asm_dependency
dependency_condition <ASM MNP package_name>=up dependency_location same_node
If SGeRAC packages are configured in the same cluster, then the ASM MNP package should not be created and the Oracle database package should depend on the SGeRAC Clusterware package instead of the ASM MNP. In this case, use the definition below instead of the one above this paragraph:
DEPENDENCY_NAME asm_dependency
DEPENDENDY_CONDITION <SGeRAC OC MNP PACKAGE_NAME>=UP
DEPENDENCY_LOCATION SAME_NODE
Since LVM logical volumes are used in disk groups, specify the name(s) of the volume groups on which the ASM diskgroups reside on, for the attribute "vg".
Configure the ip_subnet and ip_address parameters.
Configure the toolkit parameterTKIT_DIR. This parameter is synonymous to the legacy package directory (for example, /etc/cmcluster/dg1_package). On a cmapplyconf, TKIT_DIR will contain the toolkit configuration file haoracle.conf on all configured nodes. Note that the TKIT_DIR for this package should be different from the TKIT_DIR configured for the ASM MNP.
Configure the other toolkit parameters for the database package as mentioned in “Support For Oracle Database without ASM” (page 9) for the database failover legacy package.
Apply the package configuration using:
# cmapplyconf
This command "applies" the package configuration to the CDB (Serviceguard Configuration Database). It also creates toolkit configuration directory defined by TKIT_DIR on all target nodes, if not already present and then creates the toolkit configuration file in it with the values specified in the db1pkg.conf file.
For more information on modular packages, see whitepaper Modular package support in Serviceguard for Linux and ECM Toolkits available at http://www.hp.com/go/
Also refer the whitepaper Migrating Packages from Legacy to Modular Style, October 2007 for more information. You can find this whitepaper at http://www.hp.com/go/
3.To configure a ECMT modular failover package for an Oracle database using ASM in a Serviceguard cluster where SGeRAC packages are also running.