>-----Original Message----- >From: oracle-l-bounce@xxxxxxxxxxxxx=20 >[mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Hitchman, Peter >Sent: Tuesday, November 09, 2004 6:33 AM >To: oracle-l@xxxxxxxxxxxxx >Subject: RE: TNS_ADMIN > > >Hi, >My experience on Solaris with Oracle 9i is that it looks in >$ORACLE_HOME/network/admin first, but I am sure that different=20 >ports vary, >despite what the manual say. I suggest using truss on a=20 >tnsping or sqlplus >session and studying the ouput for open commands to see what order the >search takes place in for the tnsnames.ora file. > >Regards > >Pete > I had similar experience with a Sequent. Oracle insisted on looking for (and finding) a tnsnames.ora at $ORACLE_HOME/network/admin, and, having found it, ignoring any TNS_ADMIN setting. This was, of course, contrary to what the release notes said. My hack was to set a totally bogus TWO_TASK (two wrongs make a right?). Oracle then would try to resolve the bogus service name using $ORACLE_HOME/network/admin/tnsnames.ora, fail, and then as a last resort look for $TNS_ADMIN/tnsnames.ora. -- //www.freelists.org/webpage/oracle-l