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

Home -> Community -> Usenet -> c.d.o.server -> Re: Shared Server Configuration: When exactly is the connect to the dispatcher established?

Re: Shared Server Configuration: When exactly is the connect to the dispatcher established?

From: Howard J. Rogers <hjr_at_dizwell.com>
Date: Wed, 01 Sep 2004 21:13:16 +1000
Message-ID: <4135aeeb$0$9811$afc38c87@news.optusnet.com.au>


Howard J. Rogers wrote:

[snip]

Incidentally, I meant to add that having been routed through to a particular instance, and a particular dispatcher, you are stuck with that assignment, even if the conditions that got you there change dramatically.

My earlier example had you connecting through to node B because it's CPU load was only 40%. Well... once you connect, you may find that a colleague has just that minute started the biggest, nastiest select statement you've seen in your life. CPU load shoots to over 90% and stays there for minutes on end.... Tough. You've been assigned to that node, and there you must stay.

There is, in other words, nothing clever about RAC along the lines of 'let me quietly re-assign you to another node, because this one's getting bogged down'. We have Resource Manager to try and manage those sorts of problems (preferably before they arise), and RM is (of course) not a RAC-specific thing.

Regards
HJR Received on Wed Sep 01 2004 - 06:13:16 CDT

Original text of this message

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