Which three statements are true concerning node evictions and reboots performed by Oracle Clusterware 12c?

Question

Options

• AAll node evictions require that the evicted node or nodes be rebooted.
• BA node whose performance is severely degraded can be evicted.
• CThe OCSSD process may evict a node after an escalation request from a database instance
• DThe CSSDMONITOR process can request a node eviction.
• EThe OCLSKD process is used for node eviction requests originating on the node to be evicted.
• FThe reboot advisory broadcasts reboot decisions only over the interconnect.

• A
  4% (1)
• B
  78% (18)
• C
  13% (3)
• F
  4% (1)

Explanation

D: The cssdagent and cssdmonitor provide the following services to guarantee data integrity: Monitors the CSS daemon; if the CSS daemon stops, then it shuts down the node Monitors the node scheduling to verify that the node is not hung, and shuts down the node on recovery from a hang. Note If the Oracle Clusterware itself is working perfectly but one of the RAC instances is hanging , the database LMON process will request a member kill escalation and ask the CSS process to remove the hanging database instance from the cluster. On a Linux/Unix system CSS consists of ocssd.bin, cssdmonitor, and cssdagent. E: Cluster kill daemon (oclskd) handles instance/node evictions requests that have been escalated to the Cluster Synchronization Service (CSS). Incorrect Answers: C: Ocssd manages cluster node membership and runs as the oracle user; failure of this process results in a node restart.

No community discussion yet for this question.