Re: Oracle RAC nodes eviction question

From: Seth Miller <sethmiller.sm_at_gmail.com>
Date: Wed, 13 Aug 2014 16:32:13 -0500
Message-ID: <CAEueRAVr7+umXr_sZv2kBP2SAFoGmSSDeyHGHaQgmNCR3f6tLQ_at_mail.gmail.com>



Amir,

The first question is, why was the node evicted. The answer to that should be pretty clear in the clusterware alert log. If the binaries go away for any amount of time, cssdagent or cssdmonitor will likely see that as a hang and initiate a reboot.

Seth Miller

On Wed, Aug 13, 2014 at 2:57 PM, Hameed, Amir <Amir.Hameed_at_xerox.com> wrote:

> Folks,
>
> I am trying to understand the behavior of an Oracle RAC Cluster if the
> Grid and RAC binaries homes become unavailable while the Cluster and Oracle
> RAC are running. The Grid version is 11.2.0.3 and the platform is Solaris
> 10. The Oracle Grid and the Oracle RAC environments are on NAS with the
> database configured with dNFS. The storage for Grid and RAC binaries are
> coming from one NAS head whereas the OCR and Voting Disks (three of each)
> are spread over three NAS heads so that in the event that one NAS head
> becomes unavailable, the cluster can still access two voting disks. The
> recommendation for this configuration came from the storage vendor and
> Oracle. What we observed was that last weekend when the NAS head where the
> Grid and RAC binaries were mounted from went down for a few minutes, all
> RAC nodes were rebooted even though two voting disks were still accessible.
> In my destructive testing about a year ago, one of the tests run was to
> pull all cables of NICs that were used for kernel NFS on one of the RAC
> nodes but the cluster did not evict that node. Any feedback will be
> appreciated.
>
>
>
> Thanks,
>
> Amir
>

--
http://www.freelists.org/webpage/oracle-l
Received on Wed Aug 13 2014 - 23:32:13 CEST

Original text of this message