Troubleshooting Instance Evictions (Instance terminates with ORA-29740, Instance Abort, Instance Kill)
(Doc ID 1549135.1)
Last updated on AUGUST 04, 2018
Applies to:Oracle Database - Enterprise Edition - Version 18.104.22.168 and later
Information in this document applies to any platform.
Purpose: Understanding and Troubleshooting Instance Evictions.
Symptoms of an instance eviction: Instance terminates with ORA-29740, Instance Abort, Instance Kill
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
|What is an instance eviction?|
|Why do instances get evicted?|
|How can I tell that I have had an instance eviction?|
|What is the most common cause of instance evictions?|
|Key files for troubleshooting instance evictions|
|Steps to diagnose instance evictions|
|Step 1. Look in the alert logs from all instances for eviction message.|
|Step 2. For ora-29740, check the lmon traces for eviction reason.|
|1. Find the reason for the reconfiguration.|
|2. Understand the reconfiguration reason|
|Step 3. Review alert logs for additional information.|
|1. "IPC Send Timeout"|
|2. "Waiting for clusterware split-brain resolution" or "Detected an inconsistent instance membership"|
|3. "<PROCESS> detected no messaging activity from instance <n>"|
|4. None of the above|
|Step 4. Checks to carry out based on the findings of steps 1, 2, 3.|
|4(a) - Network checks.|
|4(b) - Check for OS hangs or severe resource contention at the OS level.|
|4(c) - Check for database or process hang.|