Evicted Node does not reboot automatically when resources are exhausted (Doc ID 1385616.1)

Last updated on JULY 26, 2012

Applies to:

Oracle Exadata Storage Server Software - Version 11.2.2.3.2 and later
Information in this document applies to any platform.

Symptoms


One of the compute nodes in  Exadata  Machine became unresponsive.Reviewing the  logs, It is determined that the node was evicted.
 
Despite the node being evicted, the compute node does not reboot automatically- but goes into a hang/unresponsive state.

The node has to be manually power cycled to bring it back online.

Changes

 OSW shows that the memory was completely depleted leading up to the hang.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms