If resource A has a hard stop dependency on resource B, then resource A must be stopped when B stops running. The two resources may attempt to start or relocate to another server, depending upon how they are configured. Oracle recommends that resources with hard stop dependencies also have hard start dependencies.
You can configure the hard stop dependency with the following modifiers:
STOP_DEPENDENCIES=hard(intermedite:resourceB)
Use the intermediate modifier to specify whether resource B must be in either the ONLINE or INTERMEDIATE state for resource A to stay online.
STOP_DEPENDENCIES=hard(global:resourceB)
Use the global modifier to specify whether resource A requires that resource B be present on the same server or on any server in the cluster to remain online. If this constraint is not specified, then resources A and B must be running on the same server. Oracle Clusterware stops resource A when that condition is no longer met.
STOP_DEPENDENCIES=hard(shutdown:resourceB)
Use the shutdown modifier to stop the resource only when you shut down the Oracle Clusterware stack using either the crsctl stop crs or crsctl stop cluster commands.
See Also:
"STOP_DEPENDENCIES" for more information about modifiers