Re: multiple listeners
Date: Tue, 09 Apr 2002 15:15:12 GMT
Message-ID: <4ADs8.15$8E3.47092_at_news02.optonline.net>
I do not want to get into a pissing contest. I am truly interested in your view on this. What do you mean by "decreases the manageability of your configuration.". I would think it would be just the opposite." I believe that all instances should be as separate as possible. How much of a resource hog is a listener anyway. I do not believe that a separate listener per database is a resource issue, Then again, it depends on how much resources you have. I do not know how much resources a listener consumes. I do not believe it to be much. If you know, please tell me. I have always preferred a separate listener per database. This has been my company's convention long before I became a DBA, and I agree with it. Let me know your reasons behind your views. Thanks.
John
"Sybrand Bakker" <postbus_at_sybrandb.demon.nl> wrote in message
news:a20d28ee.0204080208.90cd2f7_at_posting.google.com...
> "news-server.optonline.net" <j_at_aol.com> wrote in message
news:<OQJr8.188291$u77.38389928_at_news02.optonline.net>...
> > The way we work it is the listener name would be listener_sid. We have
one
> > listener per database. I do not see what the issue with that is. This
way,
> > if you are doing work on one database, you can bring down the listener
> > without affecting other databases. You can, in your listener.ora file,
give
> > other databases per listener in the sid_list. Do what you want.
> >
> > John
> >
>
> This is an obvious waste of resources, and also decreases the
> manageability of your configuration.
> Excluding users from a database can be done be enabling restricted
> session mode.
> This will of course not work, when all your users have the DBA role,
> which might well be true in your situation.
>
> Regards
>
> Sybrand Bakker
> Senior Oracle DBA
Received on Tue Apr 09 2002 - 17:15:12 CEST