Re: New database servers...one listener or one for each database.
Date: Mon, 14 Jul 2014 10:31:41 -0600
Message-ID: <53C405ED.7060700_at_gmail.com>
On 14/07/2014 9:27 AM, Chris Grabowy wrote:
>
> So were migrating all the production databases to new Red Hat servers.
>
> The question being debated by the DBAs is…
>
> - One listener for all the databases (1-10) on the server?
>
> - One listener per database, different ports, on the server?
>
If they want to have additional busy-work during their administration, then definitely use one listener per database.
Otherwise, consider that the listener is only used during the initial communication, and once a session is established the listener can be taken down without impacting the session.
A much more important decision is who to configure the connection pools used by the middle tier. The is a frequent incorrectly designed "session per lookup" problem that needs to be addressed.
Then again, a listener has only a limited number of connections it can handle per second (because we spawn/fork-exec full processes) and if we exceed that rate, we will get a variety of failures that may be difficult to understand. The exact rate needs to be tested on your specific hardware.
I'd be curious as to what 'their' arguments are for either option.
/Hans
-- http://www.freelists.org/webpage/oracle-lReceived on Mon Jul 14 2014 - 18:31:41 CEST