-
1. Re: Oracle and TNS_NAMES
We always install Oracle client and set the TNS_ADMIN system environmental variable to point to the directory that contains our tnsnames.ora file, e.g.
TNS_ADMIN=C:\oracle\product\11.2.0\client_1\network\admin
-
2. Re: Oracle and TNS_NAMES
But you don't actually need to install an Oracle Client as Tableau Server comes with this built-in, so is the System Environment variable method the only way to set the TNS_NAMES location in this case?
-
3. Re: Oracle and TNS_NAMES
Hi Eric, that's the only way I know of doing it I'm afraid. Where did you see that Oracle was deprecating the environment variable out of interest?
-
4. Re: Oracle and TNS_NAMES
The client might be built in, but its configuration is not.
You essentially have two choices: either configure the TNS_ADMIN env variable as everyone here is suggestion, or train all your Publishers to use the hack of copy-pasting the entire TNSnames.ora entry, replete with parentheses, into the Connection dialog in their Workbooks. We have been doing this for quite a while in our evironment, because it's not possible to keep up with the many hundreds of unique TNSnames.ora entries that exist across many hundreds of Workbooks. But our environment is "unique" in this regard.
-
5. Re: Oracle and TNS_NAMES
I've asked my colleague who mentioned deprecating the environment variable and it looks like it may not be entirely correct. The original post which referred to this is: https://community.oracle.com/message/11179463
but this only refers to a specific ODP test case.
I think therefore that the environment variable method is still supported by Oracle and of course Tableau.
-
-