Evicted Node does not reboot automatically when resources are exhausted
(Doc ID 1385616.1)
Last updated on FEBRUARY 22, 2019
Applies to:Oracle Exadata Storage Server Software - Version 220.127.116.11.2 and later
Information in this document applies to any platform.
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.
OSW shows that the memory was completely depleted leading up to the hang.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!