A closer look on Resource Dependencies
Database resource - Status:
# crsctl status resource ora.grac4.db
NAME=ora.grac4.db
TYPE=ora.database.type
TARGET=ONLINE , ONLINE , ONLINE
STATE=ONLINE on grac41, ONLINE on grac42, ONLINE on grac43
--> database is running on grac41
Database resource - Configuration:
# crsctl status resource ora.grac4.db -p | egrep '^NAME|DEPEND'
NAME=ora.grac4.db
START_DEPENDENCIES=hard(ora.DATA.dg,ora.SSD.dg)
weak(type:ora.listener.type,global:type:ora.scan_listener.type,uniform:ora.ons,global:ora.gns,ora.FRA.dg)
pullup(ora.DATA.dg,ora.SSD.dg)
--> To start the DG DATA anD SSD datagroup must be already started
pullup entry means that ora.DATA.dg ora.SSD.dg are started automatically whenever resource ora.grac4.db starts
weak entry means that ora.grac4.db tries to start ora.listener.type,global:type:ora.scan_listener.type,uniform:ora.ons,global:ora.gns,ora.FRA.dg -
if any of these resoruces fails to start it has not impact on starting resource ora.grac4.db