Re: oracle names - pros/cons

Ed,

  We use Names with some success. One time I did have a problem and while talking with Oracle Support I was told "Names has been one of our problem children". But for the most part, it works well for us. We run two Names servers and we've configured our clients to access the two in a specific order (designating one as the client's primary and the other as the client's secondary server). If the primary server is down, it does take some time for the connection to timeout before proceeding to the secondary server to get the info. But this is only a minor "problem" on the initial connection. Due to this fact, we do not use names for resolving TNS entries for database links. Any database links that we have use the TNSNAMES.ORA file instead.

HTH,
Brian

Ed Stevens wrote:
>
> I have been tasked with researching the pros and cons of using Oracle
> Names Servers vs. TNSNAMES files. I know that Oracle Names is supposed
> to give you a single point of maintenance for database name resolution.
>
> In our environment (Oracle on NT, NT clients), we have used the
> TNS_ADMIN registry key to relocate the SQLNET.ORA and TNSNAMES.ORA
> files to a shared server location. This gives us the single point of
> maintenance offered by Oracle Names. Are there any other advantages to
> O-Names? Maintenance? Admin? Performance? Any disadvantages? I
> would expect it to be a bit of a performance hit over even our server
> shared TNSNAMES simply because it is a more complex mechanism with
> another service running on the server and broadcasting itself over the
> network, but really don't know.
>
> --
> Ed Stevens
> (Opinions are not necessarily those of my employer)
>
> Sent via Deja.com http://www.deja.com/
> Before you buy.
 

-- 
========================================
Brian Peasland
Raytheons Systems at
  USGS EROS Data Center
These opinions are my own and do not
necessarily reflect the opinions of my 
company!
========================================