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: RAC or Oracle Fail Safe

Re: RAC or Oracle Fail Safe

From: Tanel Poder <tanel.poder.003_at_mail.ee>
Date: Sun, 20 Jul 2003 16:52:56 +0300
Message-Id: <25968.338591@fatcity.com>


This is a multi-part message in MIME format.

------=_NextPart_000_00C8_01C34EDF.5EB24200 Content-Type: text/plain;

        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

RE: RAC or Oracle Fail Safe
Hi!
Of course you have to plan your servers' capacity accordingly, that in = the event of node failure, the other node will not get too loaded. When = one node crashes, the second one has to deal with queries and = transactions of both servers and we must not forget, that also rollback = of failed nodes uncommitted transactions has to be done!

Of course when you got more nodes, then the impact of one node failure = would be smaller..

Tanel.

  Here I would beg to differ. RAC is more safe. _Almost_ half of your = online user (who are on surviving node) won't even notice the node =

failure when one node in a RAC environment goes down. And those who were =
unlucky users (connected to failed node), can connect immediately to the =
surviving node, without any delay. Of course you need to configure these =
parameters manually. While in OFS environment your users have to wait = till the time surviving node brings up the database and all related = services (listener etc) completely.=20

  The price you may for these features is more money and more complex = database environment to manage.

  =20

------=_NextPart_000_00C8_01C34EDF.5EB24200 Content-Type: text/html;

        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns=3D"http://www.w3.org/TR/REC-html40" xmlns:o =3D=20
"urn:schemas-microsoft-com:office:office" xmlns:w =3D=20 "urn:schemas-microsoft-com:office:word"><HEAD><TITLE>RE: RAC or Oracle = Fail Safe</TITLE>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3DWord.Document name=3DProgId>
<META content=3D"MSHTML 6.00.2800.1141" name=3DGENERATOR>
<META content=3D"Microsoft Word 9" name=3DOriginator><LINK=20
href=3D"cid:filelist.xml_at_01C34E0C.4E759A50" rel=3DFile-List><!--[if gte = mso 9]><xml>
 <o:OfficeDocumentSettings>
  <o:DoNotRelyOnCSS/>
 </o:OfficeDocumentSettings>
</xml><![endif]--><!--[if gte mso 9]><xml>
 <w:WordDocument>

  <w:Zoom>0</w:Zoom>
  <w:DocumentKind>DocumentEmail</w:DocumentKind>
  <w:EnvelopeVis/>

 </w:WordDocument>
</xml><![endif]-->
<STYLE>@font-face {

        font-family: Tahoma;
}
@page Section1 {size: 8.5in 11.0in; margin: 1.0in 1.25in 1.0in 1.25in; = mso-header-margin: .5in; mso-footer-margin: .5in; mso-paper-source: 0; } P.MsoNormal {

        FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"; = mso-style-parent: ""; mso-pagination: widow-orphan; = mso-fareast-font-family: "Times New Roman" }
LI.MsoNormal {

        FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"; = mso-style-parent: ""; mso-pagination: widow-orphan; = mso-fareast-font-family: "Times New Roman" }
DIV.MsoNormal {

        FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"; = mso-style-parent: ""; mso-pagination: widow-orphan; = mso-fareast-font-family: "Times New Roman" }
A:link {

        COLOR: blue; TEXT-DECORATION: underline; text-underline: single }
SPAN.MsoHyperlink {

        COLOR: blue; TEXT-DECORATION: underline; text-underline: single }
A:visited {

        COLOR: blue; TEXT-DECORATION: underline; text-underline: single }
SPAN.MsoHyperlinkFollowed {

        COLOR: blue; TEXT-DECORATION: underline; text-underline: single }
P.MsoAutoSig {

        FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"; = mso-pagination: widow-orphan; mso-fareast-font-family: "Times New Roman" }
LI.MsoAutoSig {

        FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"; = mso-pagination: widow-orphan; mso-fareast-font-family: "Times New Roman" }
DIV.MsoAutoSig {

        FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"; = mso-pagination: widow-orphan; mso-fareast-font-family: "Times New Roman" }
P {

        FONT-SIZE: 12pt; MARGIN-LEFT: 0in; MARGIN-RIGHT: 0in; FONT-FAMILY: = "Times New Roman"; mso-pagination: widow-orphan; = mso-fareast-font-family: "Times New Roman"; mso-margin-top-alt: auto; = mso-margin-bottom-alt: auto
}
SPAN.EmailStyle19 {

        COLOR: navy; mso-style-type: personal; mso-ansi-font-size: 10.0pt; = mso-ascii-font-family: Arial; mso-hansi-font-family: Arial; = mso-bidi-font-family: Arial
}
SPAN.EmailStyle20 {

        COLOR: #993366; mso-style-type: personal-reply; mso-ansi-font-size: = 10.0pt; mso-ascii-font-family: Arial; mso-hansi-font-family: Arial; = mso-bidi-font-family: Arial
}
DIV.Section1 {

        page: Section1
}
OL {

        MARGIN-BOTTOM: 0in
}
UL {

        MARGIN-BOTTOM: 0in
}
</STYLE>
</HEAD>
<BODY lang=3DEN-US style=3D"tab-interval: .5in" vLink=3Dblue link=3Dblue =

bgColor=3D#e0e0e0><![if !supportEmptyParas]><![endif]><![if =

!supportEmptyParas]><![endif]><![if !supportEmptyParas]><![endif]><![if =
!supportEmptyParas]><![endif]><![if !supportEmptyParas]><![endif]><![if =
!supportEmptyParas]><![endif]><![if !supportEmptyParas]><![endif]><![if =
!supportEmptyParas]><![endif]><![if !supportEmptyParas]><![endif]><![if =
!supportEmptyParas]><![endif]>

<P class=3DMsoNormal><SPAN class=3DEmailStyle19><FONT face=3DArial =
color=3Dnavy=20
size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: = 12.0pt"><o:p></o:p></SPAN></FONT></SPAN></P><![if = !supportEmptyParas]><![endif]>
<DIV><SPAN class=3DEmailStyle19><FONT face=3DArial color=3Dnavy =
size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: = 12.0pt"><FONT=20
color=3D#000000>Hi!</FONT></SPAN></FONT></SPAN></DIV>
<DIV><SPAN class=3DEmailStyle19><FONT face=3DArial color=3Dnavy =
size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: = 12.0pt">Of=20
course you have to plan your servers' capacity accordingly, that in the = event of=20
node failure, the other node will not get too loaded. When one node = crashes, the=20
second one has to deal with queries and transactions of both servers and = we must=20
not forget, that also rollback of failed nodes uncommitted transactions = has to=20
be done!</SPAN></FONT></SPAN></DIV>
<DIV><SPAN class=3DEmailStyle19><FONT face=3DArial color=3Dnavy =
size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: = 12.0pt"></SPAN></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3DEmailStyle19><FONT face=3DArial color=3Dnavy =
size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: = 12.0pt">Of=20
course when you got more nodes, then the impact of one node failure = would be=20
smaller..</SPAN></FONT></SPAN></DIV>
<DIV><SPAN class=3DEmailStyle19><FONT face=3DArial color=3Dnavy =
size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: = 12.0pt"></SPAN></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3DEmailStyle19><FONT face=3DArial color=3Dnavy =
size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: = 12.0pt">Tanel.</SPAN></FONT></SPAN></DIV>
<DIV><SPAN class=3DEmailStyle19><FONT face=3DArial color=3Dnavy =
size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: = 12.0pt"></SPAN></FONT></SPAN>&nbsp;</DIV>
<BLOCKQUOTE dir=3Dltr=20

style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; = BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">   <DIV class=3DSection1>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 0.5in"><SPAN = class=3DEmailStyle20><FONT=20
  face=3DArial color=3D#993366 size=3D2><SPAN=20   style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: = 12.0pt">Here I=20
  would beg to differ. RAC is more safe. _<I><SPAN=20   style=3D"FONT-STYLE: italic">Almost</SPAN></I>_ half of your online = user (who=20
  are on surviving node) won=92t even notice the node failure when one = node in a=20
  RAC environment goes down. And those who were unlucky users (connected = to=20
  failed node), can connect immediately to the surviving node, without = any=20
  delay. Of course you need to configure these parameters manually. = While in OFS=20
  environment your users have to wait till the time surviving node = brings up the=20
  database and all related services (listener etc) completely.=20   <o:p></o:p></SPAN></FONT></SPAN></P>
  <P class=3DMsoNormal style=3D"MARGIN-LEFT: 0.5in"><SPAN = class=3DEmailStyle20><FONT=20
  face=3DArial color=3D#993366 size=3D2><SPAN=20   style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: = 12.0pt">The=20
  price you may for these features is more money and more complex = database=20
  environment to manage.<o:p></o:p></SPAN></FONT></SPAN></P><![if = !supportEmptyParas]><![endif]>
  <P class=3DMsoNormal><SPAN class=3DEmailStyle20><FONT face=3DArial = color=3D#993366=20
  size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
12.0pt">&nbsp;</SPAN></FONT></SPAN><![if =
!supportEmptyParas]><![endif]><![if !supportEmptyParas]><![endif]><![if =
!supportEmptyParas]><![endif]><![if !supportEmptyParas]><![endif]><![if =
!supportEmptyParas]><![endif]><![if !supportEmptyParas]><![endif]><![if =
!supportLists]><![endif]><![if !supportLists]><![endif]><![if =
!supportLists]><![endif]><![if !supportLists]><![endif]><![if =
!supportLists]><![endif]><![if !supportLists]><![endif]><![if =
!supportEmptyParas]><![endif]><![if !supportEmptyParas]><![endif]><![if = !supportEmptyParas]><![endif]><![if !supportEmptyParas]><![endif]><![if = Received on Sun Jul 20 2003 - 08:52:56 CDT

Original text of this message

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