According Oracle these locations are searched for tnsnames.ora
, resp. sqlnet.ora
and ldap.ora
:
- Oracle Net files in present working directory (PWD/CWD)
TNS_ADMIN
defined sessionally or by user-defined scriptTNS_ADMIN
defined as a global environment variableTNS_ADMIN
defined in the registry- Oracle Net files in
%ORACLE_HOME/network|net80\admin
(Oracle default location)
However, I am not sure whether each application/driver follows this list. I got this list from Oracle Document 111942.1 referring to Oracle 9i, so it might be outdated.
In Database Net Services Administrator’s Guide the order is
TNS_ADMIN
defined by environment variableTNS_ADMIN
defined in the registry (ifTNS_ADMIN
environment variable is not present)%ORACLE_HOME%/network/admin
directory (ifTNS_ADMIN
environment variable is not present)
I would recommend to define an environment variable for TNS_ADMIN
and use only one tnsnames.ora file. In order to be on the safe side, check also your registry values.
If your files are not located in %ORACLE_HOME%\network\admin
, I recommend to create a symbolic link for it – just to be on the very safe side, e.g. mklink /d %ORACLE_HOME%\network\admin c:\Oracle\common\settings\admin
Another note, you don’t have to “play” with your tnsnames.ora file. With Process Monitor from Microsoft Sysinternals you can monitor each file access, i.e. the filter would be Path contains tnsnames
Update
When I run a test on my machine I get following order:
- Environment variable
TNS_ADMIN
- Registry Key
HKEY_CURRENT_USER\SOFTWARE\ORACLE\KEY_{Oracle_Home_Name}\TNS_ADMIN
-
Registry Key
HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\KEY_{Oracle_Home_Name}\TNS_ADMIN
, resp.HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\ORACLE\KEY_{Oracle_Home_Name}\TNS_ADMIN
-> Only if
TNS_ADMIN
Environment variable is not set. %ORACLE_HOME%\network\admin
- Current directory (which can be different to directory where your application is located)
- Folder where your application is located
Update 2
Obviously there is no fix search, it varies for different providers/drivers. Maybe it also depends on the Oracle version.
For example, the Oracle HTTP Server reads TNS_ADMIN
setting from opmn.xml
config file.
Another example, for ODP.NET Managed Driver (Oracle.ManagedDataAccess) beta version, I found this order at Oracle Managed and TNS Names :
- data source alias in the ‘dataSources’ section under
<oracle.manageddataaccess.client>
section in the .NET config file (i.e.machine.config
,web.config
,user.config
). - data source alias in the
tnsnames.ora
file at the location specified byTNS_ADMIN
in the .NET config file. - data source alias in the
tnsnames.ora
file present in the same directory as the.exe
. - data source alias in the
tnsnames.ora
file present at%TNS_ADMIN%
(where%TNS_ADMIN%
is an environment variable setting). - data source alias in the
tnsnames.ora
file present at%ORACLE_HOME%\network\admin
(where%ORACLE_HOME%
is an environment variable setting).
In official documentation (12c Release 4 (12.1.0.2.4)) it says:
- data source alias in the
dataSources
section under<oracle.manageddataaccess.client>
section in the .NET config file (i.e.machine.config
,web.config
,user.config
). - data source alias in the
tnsnames.ora
file at the location specified byTNS_ADMIN
in the .NET config file. Locations can consist of either absolute or relative directory paths. - data source alias in the
tnsnames.ora
file present in the same directory as the.exe
.
However, based on some tests I made with ODP.NET Managed Driver (4.121.2.0) it takes %ORACLE_HOME%\network\admin
and TNS_ADMIN
Environment variable into account. Locks like the documentation is not 100% correct.