RE: tnsnames.ora file maintenance

From: <>
Date: Tue, 3 Mar 2009 13:50:37 -0500
Message-ID: <>


For the Network windows users, I don't think network latency is much of an issue with a centrall located tnsnames.ora file and a TNS_ADMIN environment variable. We have that many users at least. You can put the below directory path in their sqlnet.ora files and only the tnsnames will be searched if a wrong database is issued... (not likely with applications). Ie. No OID, NTS, or other methods not listed will be searched.  

NAMES.DIRECTORY_PATH= (TNSNAMES)   For the UNIX boxes, I use the 'classic' ftp.exe <ftp://ftp.exe/> that comes with Hummingbird, (Exceed)... (not the newest ftp). I can create a profile for my tnsnames directory and have a window for every server... So my screen looks like a window where ever server has a window tiled, say eight or nine tiled windows, (including my desktop). I can then just drap the new tnsnames.ora file to each window replacing the existing one. Drag eight or nine times, and your done with the unix boxes. (I give the SQL*Server DBA a copy for her to use on her servers... don't know what she does).  

Joel Patterson
Database Administrator
904 727-2546

[] On Behalf Of Eugene Pipko Sent: Tuesday, March 03, 2009 1:39 PM
To: 'Allen, Brandon'; '' Subject: RE: tnsnames.ora file maintenance  

If I put that on the network, then every user / every server connection will have to access that same file. Will I create a network traffic, latency?

Anyone has it this way with about 300 users?  

Eugene Pipko

Seattle Pacific Industries

office: 253.872.5243

cell: 206.304.7726

P Please consider the environment before printing this e-mail.  

From: Allen, Brandon [] Sent: Tuesday, March 03, 2009 10:34 AM
To: Eugene Pipko; '' Subject: RE: tnsnames.ora file maintenance  

You can put the files on a network file share and then configure everyone to point there by setting their TNS_ADMIN environment variable, or you can use Directory Naming instead of tnsnames.  



Privileged/Confidential Information may be contained in this message or attachments hereto. Please advise immediately if you or your employer do not consent to Internet email for messages of this kind. Opinions, conclusions and other information in this message that do not relate to the official business of this company shall be understood as neither given nor endorsed by it.

Received on Tue Mar 03 2009 - 12:50:37 CST

Original text of this message