Call now: 252-767-6166  
Oracle Training Oracle Support Development Oracle Apps

 
 Home
 E-mail Us
 Oracle Articles


 Oracle Training
 Oracle Tips

 Oracle Forum
 Class Catalog


 Remote DBA
 Oracle Tuning
 Emergency 911
 RAC Support
 Apps Support
 Analysis
 Design
 Implementation
 Oracle Support


 SQL Tuning
 Security

 Oracle UNIX
 Oracle Linux
 Monitoring
 Remote s
upport
 Remote plans
 Remote
services
 Application Server

 Applications
 Oracle Forms
 Oracle Portal
 App Upgrades
 SQL Server
 Oracle Concepts
 Software Support

 Remote S
upport  
 Development  

 Implementation


 Consulting Staff
 Consulting Prices
 Help Wanted!

 


 Oracle Posters
 Oracle Books

 Oracle Scripts
 Ion
 Excel-DB  

Don Burleson Blog 


 

 

 


 

 

 
 

RAC node eviction tips

Oracle Tips by Burleson Consulting
August 27, 2008


Question:
 I understand what can cause a RAC node to be evicted from the cluster, but I can’t find the process for deciding which node will be rebooted after the eviction. Oracle’s explanations on MOSC say "a node" but in my testing it is always a particular physical machine and not the secondary instance.

What would happen in a 3 or 4 node cluster when you have a RAC node eviction? Is it safe to assume it will be instance 2 every time no matter which side of the interconnect goes down? Also what are some of the most common reasons for a node eviction?
Answer: A RAC node eviction is done on this basis. When a condition that requires a node eviction occurs (see below) The node with the lowest node number will be the node the "survives" the eviction. When you have a three node cluster, two nodes will survive a node eviction, and so on.

A node eviction is done when a heartbeat indicates that a node is not responding, and the evicted node is re-started so that it can continue to partiipate in the cluster.

 

Reason for RAC node evictions

There are many reasons for a RAC node eviction. Oracle's Cluster Health Monitor, (formerly known as the Instantaneous Problem Detector for Clusters (IPD/OS)), automatically collects OS performance metrics on a regular basis to assist with diagnosing node evictions.

 

- Hardeware Failure: A failure of any of the major hardware components (CPU, RAM, network interconnect) can cause a node eviction.

- Server Overload: A server that is expericncing RAM swapping might trigger a node eviction. It's important that each node be properly configured.

- Voting disk communications This can happen when communications to the voting disk is interrupted, causing the disconnected node to be evicted and re-boot.

- Database issues If the database (or the ASM instance) is not responding (a database "hang" condition), then a node eviction may occur.


 

 

��  
 
 

 
 
 
 
oracle dba poster
 

 
 
Oracle performance tuning software 
 
Oracle Linux poster
 
 
 

 

Burleson is the American Team

Note: This Oracle documentation was created as a support and Oracle training reference for use by our DBA performance tuning consulting professionals.  Feel free to ask questions on our Oracle forum.

Verify experience! Anyone considering using the services of an Oracle support expert should independently investigate their credentials and experience, and not rely on advertisements and self-proclaimed expertise. All legitimate Oracle experts publish their Oracle qualifications.

Errata?  Oracle technology is changing and we strive to update our BC Oracle support information.  If you find an error or have a suggestion for improving our content, we would appreciate your feedback.  Just  e-mail:  and include the URL for the page.


                    









Burleson Consulting

The Oracle of Database Support

Oracle Performance Tuning

Remote DBA Services


 

Copyright ? 1996 -  2014

All rights reserved by Burleson

Oracle ? is the registered trademark of Oracle Corporation.