909 views
in RAC by ACE (20,920 points)

1 Answer

by ACE (20,920 points)
  • Network failure or latency between nodes. It would take 30 consecutive missed checkins (by default - determined by the CSS misscount) to cause a node eviction. 
  • Problems writing to or reading from the CSS voting disk.  If the node cannot perform a disk heartbeat to the majority of its voting files, then the node will be evicted.
  • A member kill escalation.  For example, database LMON process may request CSS to remove an instance from the cluster via the instance eviction mechanism.  If this times out it could escalate to a node kill. 
  • An unexpected failure or hang of the OCSSD process, this can be caused by any of the above issues or something else.
  • An Oracle bug.
...