Re: multiple tnsnames.ora files

> > I have seen many articles on maintaining multiple tnsnames.ora files so that
> > individual groups can use each file which only points to the databases they
> > need to see. This seems like a great idea. Why give a global file
> >
> > I wanted to see if others out there are doing this and does it work? Some
> > say it is not easy to manage but I say "would you rather risk someone
> > breaking into the database because you made a global file available that
> > tells everyone how to find all of your databases?"
> >
> > Does anyone NOT recommend this? Any ideas welcome!

This idea does have some merit. But the TNSNAMES file does not give any access to any database just on it's own. They need to authenticate to the database somehow (usually userid/password). Anyone only needs to know three pieces of code to correctly configure TNSNAMES (host, port, and sid: and port is usually either 1521 and/or 1526).

It's the authentication routine that protects your system. I use a global file at my site (actually Oracle Names Server) and I don't fear anyone here breaking into any of our databases that they are not allowed access to since I don't publish userid/passwords.

It is a risk, albeit a minor one. Now I wouldn't publish my TNSNAMES info on the WWW for *everyone* and their grandparents to see, but I don't have a problem listing this info in my company.

HTH,
Brian

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