Re: how many listeners to run?
- From: "Rich Jesse" <rjoralist@xxxxxxxxxxxxxxxxxxxxx>
- To: "oracle-l" <oracle-l@xxxxxxxxxxxxx>
- Date: Thu, 10 Jan 2008 16:46:58 -0600 (CST)
Hey Li,
You may want to check out Metalink 67983.1, specifically for the QUEUESIZE
parameter for the listener.ora file.
A few scripts to use regular old SQL*Plus to throttle a Listener isn't
terribly difficult to write in Korn or Bash. At it's simplest, something
like:
-- Script 1 ("sqlconn.sh"):
sqlplus joedba/mypass@test /nolog
-- Script 2 ("hammer_listener.sh"):
i=-1
while [ $(( i += 1 )) -lt 1000 ]
do
nohup ./sqlconn.sh &
done
This is completely untested, of course. While not very robust, I hope it's
self-explanatory!
HTH! GL!
Rich
> Thank you all very much for taking your time to respond! I tend to
> agree with Freek D'Hooge to keep it simple and just use 1 listener and
> if I need to stop 1 application, I stop the corresponding database
> service of that application. My only concern with 1 listener is if it
> will be fast enough to respond to all the connection requests from the
> clients of all 4 databases not becoming a bottleneck. Any comment on
> here?
>
> Also, I have a dumb question in here. If you do multiple listeners,
> how do you prevent 1 database automatically registers itself to all
> the running listeners? ie, how do you setup database A only registers
> itself to listener A, database B only registers itself to listener B?
>
> Thanks again!
> -Li
--
//www.freelists.org/webpage/oracle-l
Other related posts:
