On Sep 23, 6:30 pm, Krish <Krishna.Bu..._at_gmail.com> wrote:
> Hi All,
> We have many unix (hp-ux, AIX, Linux, Solaris) servers running Oracle
> database 9.2.0 enterprise edition. Each server has 4 or more
> databases. Currently each unix server has its own tnsnames.ora in /etc
> folder and all windows machines TNS_ADMIN is pointing to a shared
> drive.
>
> we are planning to implement one of the below methods to avoid
> "ORA-12154" error whenever new db is created and forgot to update all
> the tnsnames.ora files.
> 1.creating TNSNames.ora in a shared (NFS mounteed) file system and
> pointing all servers TNS_ADMIN to this shared drive.
> 2.shell sciprt to replace all the tnsnames.ora files with the master
> tnsnames.ora( master tnsnames.ora file will be updated whenever new db
> is created)
>
> I would like to know the experts comments, suggestions.
>
> Thanks in advance for all your help.
>
> Krish.
#1 using the NFS mount puts all your eggs in one relatively unstable
basket (compared to a local file system)
#2 if you have so much volatility in spinning up new databases on
existing hosts already running Oracle instances, I suspect you have an
application development/deployment methodology where 1 app = 1
database - instead of 1 app = 1 schema. I've seen that before and it
is a gargantuan waste of time and money. My guess would be there's
lots of public synonyms too?
#3 I haven't used tnsnames.ora for years on a host to host database
reference in years (use @//host/service_name instead of @alias)
Received on Sun Sep 23 2007 - 21:00:41 CDT
