Here's the chain of events: Client SQLPlus logs in using client's TNS settings (TNS_Admin to = client's TNSNAMES.ORA) Client then uses a db link: Database must already have database link created Database open new connection specified by db link by using database server's TNSNames.ora In other words, since the database link is being opened by the database server, only the TNS settings on the server itself are important; the database cannot see what TNS environment the SQLPlus client is running = under. ...Rudy -----Original Message----- From: oracle-l-bounce@xxxxxxxxxxxxx = [mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Rusnak, George A. (SEC-Lee) CTR Sent: Tuesday, May 24, 2005 11:08 AM To: oracle-l@xxxxxxxxxxxxx Subject: Resolving dblinks One of our databases was started with TNS_ADMIN set to a directory where there was no TNSNAMES.ORA file. Now, when a remote user starts an = Sqlplus session and attempts to use a synonym using a dblink, the result is 'ORA-12154: TNS:could not resolve service name'. When I am logged on the host and start an Sqlplus session and use the = same synonym, the query works. How is the database link resolved when running on the host as opposed to = a session started from a remote user????=20 Thank you in advance !!! Al Rusnak Oracle Certified Professional DBA - Computer Operations * 804-734-8210 * george.rusnak@xxxxxxxx -- //www.freelists.org/webpage/oracle-l -- //www.freelists.org/webpage/oracle-l