Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Mailing Lists -> Oracle-L -> RE: oracle rac 10g and OS clusterware.

RE: oracle rac 10g and OS clusterware.

From: John Hallas <john.hallas_at_bjss.co.uk>
Date: Wed, 5 Dec 2007 14:21:09 -0000
Message-ID: <E02CB9B2777CF8459C86C49B48C48EC602BFFD50@exchange.bjss.co.uk>


Good response Dan. How often does node eviction take place on a 'normal' configuration (if there is such a thing).  

PS I came across an excellent presentation of yours this morning on HA options for Oracle

http://www.dannorris.com/wp-content/uploads/2007/11/ha-options-for-oracl e-db-oow2007-slides.pdf  

John    


From: oracle-l-bounce_at_freelists.org
[mailto:oracle-l-bounce_at_freelists.org] On Behalf Of Dan Norris Sent: 05 December 2007 03:32
To: ujang.jaenudin_at_gmail.com; Peter McLarty Cc: oracle-l_at_freelists.org
Subject: Re: oracle rac 10g and OS clusterware.  

Ujang,

Oracle Clusterware 10g will always handle node fencing (aka eviction) by rebooting one or more nodes. Oracle didn't have it's own cluster manager software for most platforms on 9i. So, if your customer was on a platform where Oracle didn't have a cluster manager of its own (it only had Linux and Windows), then building the RAC cluster would have required some 3rd party software. Some of the 3rd party cluster managers used different schemes to fence nodes from the cluster. Many of them used I/O fencing which was somewhat less disruptive in that it didn't require a node reboot, but required more proprietary interfaces to be used to access and manage storage.

The answer to your question is that it depends. You will always have to have Oracle Clusterware if you're building a 10g cluster. However, if you additionally use a 3rd party clusterware (one that uses I/O fencing instead of reboots to handle node eviction), Oracle Clusterware will not handle cluster membership and therefore won't impose its "reboot the other node" scheme of node eviction. I should mention that I believe this is true in most cases, but not all cases.

If you use just Oracle Clusterware (which is the only requirement and handles all cluster management needs albeit with using node reboots to evict them from the cluster), you'll be subject to node reboots if node eviction is required.

See Kirk McGowan's post on Oracle Clusterware's node eviction methods at http://blogs.oracle.com/kmcgowan/2007/08/09#a13 for some additional insight.

Dan  

The information included in this email and any files transmitted with it may contain information that is confidential and it must not be used by, or its contents or attachments copied or disclosed, to persons other than the intended addressee. It must not be used by, or its contents or attachments copied or disclosed to, any persons other than the intended addressee. If you have received this email in error, please notify BJSS. In the absence of written agreement to the contrary BJSS’ relevant standard terms of contract for any work to be undertaken will apply. Please carry out virus or such other checks as you consider appropriate in respect of this email. BJSS do not accept responsibility for any adverse effect upon your system or data in relation to this email or any files transmitted with it. BJSS Limited, a company registered in England and Wales (Company Number 2777575), VAT Registration Number 613295452, Registered Office Address, First Floor, Coronet House, Queen Street, Leeds, LS1 2TW

--
http://www.freelists.org/webpage/oracle-l
Received on Wed Dec 05 2007 - 08:21:09 CST

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US