11g R2 RAC : NODE EVICTION DUE TO MEMBER KILL ESCALATION


If the Oracle Clusterware itself is working perfectly but one of the RAC instances is hanging , the database LMON process will request a member kill escalation and ask the CSS process to remove the hanging  database instance from the cluster.

here apart from instance getting rebooted the node also gets rebooted.its called member kill escalation. if one instance process is not responding to other instance process like lmon, lmd etc node is perceived to be inactive and tin that case remote instance will issue instance reboot. if within 30 sec it doesn’t happen(instance is not killed or restarted) depending upon CSS miscount the node itself will reboot .

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s