Re: Question about resource's start dependency in Clusterware

Yes, if I'd like to start resource A when resource B starts I'd define a "start_dependency=pullup:always(B)" on A. However, in the example above what I'm asking about is this behaviour:

[grid_at_ractest1 ~]$ crsctl stat res -w "NAME st 'res'" -p | egrep '^NAME=|DEPEND'
NAME=res1
START_DEPENDENCIES=
STOP_DEPENDENCIES=
NAME=res2
START_DEPENDENCIES=hard(res1)
STOP_DEPENDENCIES=
[grid_at_ractest1 ~]$ crsctl start res res2

CRS-2672: Attempting to start 'res1' on 'ractest1'
CRS-2676: Start of 'res1' on 'ractest1' succeeded
CRS-2672: Attempting to start 'res2' on 'ractest1'
CRS-2676: Start of 'res2' on 'ractest1' succeeded

So, even without pullup dependencies the start of res2 caused an automatic start of res1.

Regards
Jure Bratina

To automatically start resource B when resource A is started, you need to
> use the pullup dependency.
> More information about this can be found in the clusterware administration
> and deployment guide here:
> http://docs.oracle.com/cd/E11882_01/rac.112/e41959/crschp.htm#CWADD91289
>
>

--
http://www.freelists.org/webpage/oracle-l