Re: Formula for number of DB Listeners on server

  • From: Woody McKay <woody.mckay@xxxxxxxxx>
  • To: rjoralist3@xxxxxxxxxxxxxxxxxxxxx
  • Date: Tue, 13 Oct 2015 13:03:18 -0400

Hi Rich,

All DB's are auto-registering and they are using 12.1.0.2.7 on Win64 2012
OS.



On Tue, Oct 13, 2015 at 11:59 AM, Rich J <rjoralist3@xxxxxxxxxxxxxxxxxxxxx>
wrote:

On 2015/10/13 09:58, Woody McKay wrote:


I'm part of a new team working on a new production setup for hosting. We
currently have 40 SIDs per server with one listener. Occasionally, the
listener appears to be unresponsive and the hosting team will bounce it
breaking all connections for all SIDs on the box. So, the current
configuration is not optimal.



Breaking *existing* DB connections???? If so, then that's not the
listener. And a listener bounce should really take no more than a second
or two, although if the instances are auto-registering then the outage
would be more significant.



The hosting team is working with a vendor and is proposing a server with
cpu, ram, storage that will handle upwards of 120+ SIDs. Obviously, each
SID has a different workload and number of connections based on the size of
the customer.



Oracle version? OS?

The QUEUESIZE parameter of the listener.ora can do quite a lot for
connection throughput, but it's value is specific to Oracle version and
platform. For example, in 10gR1 on AIX, the default was very low (4 or 8
maybe?), while it was boosted to 1024 in 11g. But that's just for AIX...

Rich






--
Sincerely,

WoodyMcKay

Other related posts: