RE: Oracle clusterware related question
Date: Tue, 8 May 2012 20:23:10 +0200
With 11.2 that is no longer true.
When you have configured a system management board (eg ILO, DRAC, ELOM, ...) with the clusterware, a node has the possibility to kill a non responsive node by switching of the power.
Oracle Database Administrator
tel +32(0)3 451 23 82
From: oracle-l-bounce_at_freelists.org [mailto:oracle-l-bounce_at_freelists.org] On Behalf Of Martin Berger Sent: dinsdag 8 mei 2012 20:03
Cc: tim_at_evdbt.com; Mathias.Zarick_at_trivadis.com; oracle-l_at_freelists.org Subject: Re: Oracle clusterware related question
in Oracle Clusterware no node can be evicted by the remote nodes. The 'others' can only exclude any node and hope this one commits suicide.
The problem here, on your hanging node the clusterware processes are hanging in IO to logfiles. As your NFS does not disappear, the filehandles are still open. It seems writing to logfiles is a synchronous task - so when these hang in file-IO, they can not do higher priority tasks as killing the node.
You can try to mount your log-directories 'soft' - maybe this solves the hanging issue. But I don't know which side-effects this might cause!
I am not sure if crs shows the same behavior in case logfile write hangs (as on NFS) or log file write fails (as on "mountpoints disappears as SAN-nwtwork is removed") - Mathias, do you remember the details? But as they where back in 184.108.40.206, I probably should do the testcase again.
I second Mathias, grid-logs (and also grid-binaries) should be local! All others, like rdbms binaries and logs can be on any remote system.
http://www.freelists.org/webpage/oracle-l Received on Tue May 08 2012 - 13:23:10 CDT