Re: oracle names - pros/cons

I'm not sure I see how eliminating TNSNAMES.ORA, in and of itself, is perceived as a benefit. As I mentioned in my original post, we have already centralized it to a shared copy on a single server, so we have already acheived a single point of administration -- as well as a single point of failure!

• Ed Stevens (Opinions are not necessarily those of my employer)

In article <8b0n6s$49$1_at_slb7.atl.mindspring.net>, "Phil Cook" <pncook_at_mindspring.com> wrote:
> Eliminating the tnsnames files has to be enough benefit for you to
> bear the additional administration.
>
> Names advantages
>
> Great for client server environment with multiple clients.
>
> Repository where you can see all your aliases, databases,
> etc. - query namesctl
>
> Names disadvantages
>
> The 8.1.5 java interface is not as good as the Network Manager
> Windows interface.
>
> Repository database is a single point of failure.
>
> If you don't run multiple Names servers, then you also have a
> single point of failure.
>
> More moving parts, something else to break.
>
> Setup and troubleshooting can be complex
>
>

Sent via Deja.com http://www.deja.com/
Before you buy. Received on Mon Mar 20 2000 - 00:00:00 CST