If resource A has an attraction
dependency on resource B, then Oracle Clusterware prefers to place resource A on servers hosting resource B. Dependent resources, such as resource A in this case, are more likely to run on servers on which resources to which they have attraction
dependencies are running. Oracle Clusterware places dependent resources on servers with resources to which they are attracted.
You can configure the attraction
start dependency with the following constraints:
START_DEPENDENCIES=attraction(intermediate:resourceB)
Use the intermediate
modifier to specify whether the resource is attracted to resources that are in the INTERMEDIATE
state.
START_DEPENDENCIES=attraction(type:resourceB.type)
Use the type
modifier to specify whether the dependency acts on a particular resource type. The dependent resource is attracted to the server hosting the greatest number of resources of a particular type.
Note:
Previous versions of Oracle Clusterware used the now deprecated OPTIONAL_RESOURCES
attribute to express attraction dependency.