On most servers I have only one database on the node.
Where I do have multiple databases, I have seperate ORACLE_HOMEs. Where I
have
seperate ORACLE_HOMEs, I have seperate Listeners.
There's really not much of an effort in managing multiple listeners --
after all
you have to issue a seperate sqlplus command for each database [and
also
from a seperate ORACLE_HOME each time !] , you can also issue a seperate
"lsnrctl start <listenername>" command.
I could be running 8.1.7.2, 8.1.7.3 and 9.2.0.1 on the same box.
When applying
a patchset to upgrade to 8.1.7.3 or 8.1.7.4 for one database, I do
not want to have
to stop access to the other databases. Therefore, each database has
it's own listener.
Also, try _not_ to use 1521 as the listener port so that no database
auto-registers
with a listener.
Hemant
At 04:04 AM 17-10-02 -0800, you wrote:
There has
been much discussion regarding single or multiple listeners and there
seems to be a split between those who advocate one method over the
other.
I am currently working at a site with a large
number of systems/databases.
They are well organised and one of the
standards that is in place is to have a listener per database with the
same name as the database.
The lowest port will be 1526 to avoid any
issues with auto registration on port 1521.
The whole concept works very well in my
experience; the small overhead on the server is outweighed by the ability
to stop a listener individually without affecting any other
service.
John
Hemant K Chitale
My web site page is :
http://hkchital.tripod.com
--
Please see the official ORACLE-L FAQ: http://www.orafaq.com
--
Author: Hemant K Chitale
INET: hkchital@singnet.com.sg
Fat City Network Services -- 858-538-5051 http://www.fatcity.com
San Diego, California -- Mailing list and web hosting services
---------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: ListGuru@fatcity.com (note EXACT spelling of 'ListGuru') and in
the message BODY, include a line containing: UNSUB ORACLE-L
(or the name of mailing list you want to be removed from). You may
also send the HELP command for other information (like subscribing).
Received on Thu Oct 17 2002 - 10:39:55 CDT
