This (a shared, central TNSNAMES) is exactly what we've done since 7.3. I've been told that Oracle doesn't support it, but we've never had a problem. YMMV. On the client: tns_admin=\\myserver\share_name where \\myserver\share_name contains tnsnames.ora, sqlnet.ora. Has worked quite well for us. Thanks Ed Stevens IBM Global Services - Nissan North America, Smyrna Manufacturing Plant IBM E-mail: Ed_Stevens@xxxxxxxxxx Nissan E-mail: ed.stevens@xxxxxxxxxxxxxxxxxx voice: 615.355.2988 fax: 615.223.3510 pager: 615-252-0845 -----Original Message----- From: Jesse, Rich [mailto:Rich.Jesse@xxxxxxxxxxxxxxxxx] Sent: Wednesday, September 15, 2004 11:11 AM Cc: oracle-l@xxxxxxxxxxxxx Subject: RE: Solution to 100's of Oracle clients installed with Net8 and local tnsnames.ora, sqlnet.ora I'm fearing file locking issues with this approach. Multi-platform is = another issue, although a SAMBA/NFS combo on the "central location" = should take care of that. Or are my fears unfounded? We're in the same boat, wondering what to do = about replacing the functionality of our replicated ONAMES servers for = the future. OiD 9.0.1 was not mature/stable enough to be production. = We haven't tested future versions and I don't plan to until the damnable = thing is at least free (i.e. included with our EE license). Rich -----Original Message----- Sent: Wednesday, September 15, 2004 10:32 AM Cc: oracle-l@xxxxxxxxxxxxx Subject: Re: Solution to 100's of Oracle clients installed with Net8 and local tnsnames.ora, sqlnet.ora [super snip] However once I'd got this far, it did seem appropriate to wonder if it might not be better just to set TNS_ADMIN to a central location and just have the one copy. --=20 Niall Litchfield Oracle DBA -- //www.freelists.org/webpage/oracle-l -- //www.freelists.org/webpage/oracle-l