Use the pullup start dependency if resource A must automatically start whenever resource B starts. This dependency only affects resource A if it is not running. As is the case for other dependencies, pullup may cause the dependent resource to start on any server. Use the pullup dependency whenever there is a hard stop dependency, so that if resource A depends on resource B and resource B fails and then recovers, then resource A is restarted.
Note:
Oracle recommends that resources with hard start dependencies also have pullup start dependencies.
You can configure the pullup start dependency with the following constraints:
START_DEPENDENCIES=pullup(intermediate:resourceB)
Use the intermediate modifier to specify whether resource B can be either in the ONLINE or INTERMEDIATE state to start resource A.
If resource A has a pullup dependency on multiple resources, then resource A starts only when all resources upon which it depends, start.
START_DEPENDENCIES=pullup:always(resourceB)
Use the always modifier to specify whether Oracle Clusterware starts resource A despite the value of its TARGET attribute, whether it is ONLINE or OFFLINE. By default, without using the always modifier, pullup only starts resources if the value of the TARGET attribute of the dependent resource is ONLINE.
START_DEPENDENCIES=pullup(type:resourceB.type)
Use the type modifier to specify that the dependency acts on a particular resource type.