Re: Listener

One more reason I've seen for implementing multiple listeners is ease of management. By that I mean sites that have multiple databases on one machine can set up a listener for each one. Then when the database needs to be started and stopped multiple times during maintenance, simply stop the listener and you don't need to worry about restricting access at the database level when its started. You can thus connect as the owner of the application if necessary (to pass on grants etc.) without giving the owner DBA rights that you may forget to remove.

HTH. Pete

Erwin Dondorp wrote:

> DerKommisar wrote:
> > Is There a max value of concurrent sessions for an only Listener ?
> > [listener.ora sample removed]
> > This LISTENER above, with this Port (1521) is able than has also 300 users
> > at the same time?
> > Or I have to do another Listener (ex. LIST1) with another Port (ex. 1526) ?
>
> The listener only sets up connections.
> Once a connection is made, the listener is not involved any more.
> Proof: You can shutdown the listener without existing connections being
> dropped.
>
> The main reason for having multiple listeners or a configuration
> involving MTS
> is the speed at which new connections are being made.
> If the rate of new connections is too high, the OS will spend too much
> time starting
> up the new shadow processes.
> e.g. MTS will cause some shadow processes to be started in advance.
>
> If these 300 users all execute horribly statements then the result is a
> very slow database.
> That should be taken into account as well.
> Otherwise there is no upper limit to the number of connections.
> (And how about the user licences :-)
>
> Erwin
> --
> Erwin Dondorp
> <http://www.dondorp.com/>

Received on Mon Jan 24 2000 - 11:36:08 CST