Re: Oracle clusterware related question

From: Tim Gorman <>
Date: Tue, 08 May 2012 09:32:19 -0600
Message-ID: <>

Your phrase "/kept showing that the node was still part of the cluster/" doesn't mention how long that state lasted. Clearly, from your email, it lasted too long, but equally obviously, at some point the clusterware reacted, and I'm wondering how long that wait might have been?

Armed with that information about how long it took for the clusterware to react in mind, I'd suggest using the "crsctl query css" command as suggested here in the 11.2 docs online...

            /crsctl get css/

    /Use the |crsctl get css| command to obtain the value of a specific     Cluster Synchronization Services parameter./



/crsctl get cssparameter

    /Usage Notes/


/Cluster Synchronization Services parameters include:/



/This command only affects the local server/


    /To display the value of the |disktimeout| parameter for CSS, use     the following command:/

    /$ crsctl get css disktimeout
    200 /

So, you may want to share what the values for "disktimeout" and "misscount" were, and whether those values corroborated at all with your observations?

Hope this helps?

Tim Gorman
consultant ->  Evergreen Database Technologies, Inc.
postal     =>  PO Box 352151, Westminster CO 80035
website    =>
email      =>
mobile     =>  +1-303-885-4526
fax        =>  +1-303-484-3608
Lost Data? => for info about DUDE...

On 5/8/2012 8:41 AM, Hameed, Amir wrote:
> Folks,
> I have a three-node Oracle RAC running with Grid version So,
> far there is no database created and only CRS is running on all nodes. I
> am using NFS for everything (binaries, OCR&  voting disk and database
> files). Each server has two 10GbE NICs for dNFS. The binaries, OCR and
> voting disks are on an aggregated link (two 1GbE NIC). The OS is Solaris
> 10.
> While doing destructive testing to validate configuration and to observe
> behavior in extreme scenarios, when we pulled cables on one RAC server
> from both NICs that are part of the aggregated link for the binaries,
> voting disk and OCR, I was expecting that because CRS would not be able
> to access the voting disks on that node to update its status,
> clusterware would eject that node from the cluster. The "crsctl status
> resource -t" command from the other nodes kept showing that the node was
> still part of the cluster. I am trying to understand this behavior and
> would appreciate if someone can explain it.
> Thanks
> Amir
> --

Received on Tue May 08 2012 - 10:32:19 CDT

Original text of this message