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, fail over and timeout .. Big Question

RE: RAC, fail over and timeout .. Big Question

From: Jamadagni, Rajendra <Rajendra.Jamadagni_at_espn.com>
Date: Thu, 12 Jun 2003 11:37:35 -0700
Message-ID: <F001.005B0774.20030612110133@fatcity.com>

<FONT face="Courier New" color=#0000ff

size=2>Thanks KG, Greg,
<FONT face="Courier New" color=#0000ff

size=2> 
<FONT face="Courier New" color=#0000ff

size=2>What I visualize is this ...
<FONT face="Courier New" color=#0000ff

size=2> 
<FONT face="Courier New" color=#0000ff

size=2>Specify a (sort of) timeout value. If query doesn't come back within this value, raise alert and fail over to the other side. If you get the same problem, raise the hell out of everyone and go to cache mode (good for 3-5 minutes). Hope the problem gets fixed by then.
<FONT face="Courier New" color=#0000ff

size=2> 
<FONT face="Courier New" color=#0000ff

size=2>The biggest question is how to timeout a query if it doesn't return in specified time? We got some good VB coders ... so any ideas with VB are also welcome.
<FONT face="Courier New" color=#0000ff

size=2> 
<FONT face="Courier New" color=#0000ff

size=2>Pre-connecting is something we are looking at, but sometimes application performs DML as well. So ... the plot thickens ...
<FONT face="Courier New" color=#0000ff

size=2> 
<FONT face="Courier New" color=#0000ff

size=2>I am still researching ...
<FONT face="Courier New" color=#0000ff

size=2>Raj
<FONT face="Courier New"

size=2>-------------------------------------------------------------------------------- 
Rajendra dot Jamadagni at nospamespn dot com All Views expressed in this email
are strictly personal. QOTD: Any clod
can have facts, having an opinion is an art !

  <FONT face=Tahoma
  size=2>-----Original Message-----From: Loughmiller, Greg   [mailto:[EMAIL PROTECTED]Sent: Thursday, June 12, 2003   2:35 PMTo: Multiple recipients of list ORACLE-LSubject:   RE: RAC, fail over and timeout .. Big Question   It
  would be interesting to see if the pre-connect helps you out or not.. We are   getting ready to work thru similar issues/testing...   <SPAN
  class=600273317-12062003> 
  <SPAN
  class=600273317-12062003>Greg   

    <FONT face="Times New Roman"
    size=2>-----Original Message-----From: K Gopalakrishnan     [mailto:[EMAIL PROTECTED]Sent: Thursday, June 12, 2003 12:30     PMTo: Multiple recipients of list ORACLE-LSubject: RE:     RAC, fail over and timeout .. Big Question     <FONT face=Arial color=#0000ff
    size=2>Raj:
    <FONT face=Arial color=#0000ff
    size=2> 
    I
    am afraid, there are not much alternatives you can think of. Even the SELECT     fail over
    <FONT face=Arial color=#0000ff
    size=2>will  take around few seconds since it has to attach     the PGA to the second
    <FONT face=Arial color=#0000ff
    size=2>instance and run the query from where it is failovered, though you     can overcome
    <FONT face=Arial color=#0000ff
    size=2>this by enabling pre-connect.     <SPAN
    class=576224803-13062003><FONT face=Arial color=#0000ff     size=2> 
    <SPAN
    class=576224803-13062003>Pls let me know if you got any nice ideas     ;)
    <SPAN
    class=576224803-13062003> 
    Best Regards,K Gopalakrishnan
    <FONT face=Tahoma
    size=2>-----Original Message-----From: [EMAIL PROTECTED]     [mailto:[EMAIL PROTECTED]On Behalf Of Jamadagni,     RajendraSent: Thursday, June 12, 2003 7:50 AMTo:     Multiple recipients of list ORACLE-LSubject: RAC, fail over and     timeout .. Big Question
    Hi all,
    here is a (hopefully) tricky one
    ...
    We have a two node RAC (9202), two
    applications run on either side, no problems there. We have a business     critical process that runs all the time on node T2. This process needs to     have a set response time or it affects business. And it is written in VB.     Currently we have already handled the situations when a node is down (or     machine is down) it fails over to the other side and continues.     What we need to cater for is when DB is     up, but sick (i.e. not responding). We need to be able to specify a timeout     in the queries and when we get no response in the specified time, we need to     automatically fail over to the other side.     The queries in the application are
    optimally written, they are sub-second or single digit second queries. So, a     query taking a long time would be about 10-15 seconds.     While we are fishing for ideas, has     anyone implemented anything like this? Any ideas?     Thanks in advance <FONT
    face="Courier New" size=2>Raj <FONT face="Courier New"

    size=2>-------------------------------------------------------------------------------- 
    Rajendra dot Jamadagni at nospamespn dot     com All Views expressed in this
    email are strictly personal. <FONT face="Courier New"     size=2>QOTD: Any clod can have facts, having an opinion is an art !     
********************************************************************This e-mail 
message is confidential, intended only for the named recipient(s) above and may contain information that is privileged, attorney work product or exempt from disclosure under applicable law. If you have received this message in error, or are not the named recipient(s), please immediately notify corporate MIS at (860) 766-2000 and delete this e-mail message from your computer, Thank
you.*********************************************************************2
Received on Thu Jun 12 2003 - 13:37:35 CDT

Original text of this message

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