CRS invoked node reboot due to Timesten resource unresponsive after private network was down
Last updated on MAY 08, 2018
Applies to:Oracle TimesTen In-Memory Database - Version 220.127.116.11.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
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