CRS invoked node reboot due to Timesten resource unresponsive after private network was down
(Doc ID 2354140.1)
Last updated on FEBRUARY 21, 2019
Applies to:Oracle TimesTen In-Memory Database - Version 188.8.131.52.17 and later
Information in this document applies to any platform.
Customer was observing that when interconnect network was down , CRS was rebooting one of the node. After further checking it was found that CRS is attempting reboot as some of the Timesten resource did not clean up on time.
Here is the series of events and timelines taken from the logs
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document