Issue with TNSNames.Ora and ODAC 9.6.20

[kithran]

To ensure our customers connect to the correct database when they have multiple instances (e.g. a live database and a test database) they have normally created specific tnsnames.ora files that only have the connection details for a single database that are then placed in the same directory as the exe files.

Previously with this arrangement when running an exe from that location users would only have a single database to choose from however with an exe built with ODAC 9.6.20 this local copy of the tnsnames.ora file is being ignored and instead the main one in the oracle directory is being used leading to the user being presented with multiple databases they can connect to.

Is this a deliberate change?
If so can the old behaviour be regained via a change to our code?
If not is there an eta on a fix?

[AlexP]

Hello,

Thank you for the information. We have turned back the old behavior. From now, the tnsnames.ora file will be searched for at the following locations:
1) application local folder;
2) the TNS_ADMIN environmental variable;
3) the TNS_ADMIN registry parameter;
4) client installation folder.

[ccedotal]

9.6.22 was just released and this fix is not in it. Can you tell us which version to expect it in, and possibly when?

[AlexP]

The current ODAC version works correctly with the TNS_ADMIN environment parameter. Please describe the issue in more details.