I wanted an NT client machine to use a remote tnsnames.ora file and not
the local tnsnames.ora found in the network\admin directory. The method
that usually works is to create a registry entry TNS_ADMIN which points to
the remote tnsnames.ora. In the past week I have had mixed results employing
this method on 2 different machines. On one client machine running a brio
application both the application and the tnsping utility were pointing to
the remote tnsnames file . However sqlplus was still looking at the local
tnsnames file. Does anybody know what could be causing this.
On a separate client machine the TNS_ADMIN worked for all oracle
applications like Quest SQL navigator etc) but the Microsoft Access program
could no longer attach to oracle tables (it still wanted to use the local
tnsnames.ora)
Does anybody know if there is another parameter besides TNS_ADMIN that
controls where sqlnet looks for the tnsnames,ora file,
Thanks,
Received on Wed Sep 20 2000 - 21:37:20 CDT
