My Oracle Support Banner

19C ODPM Driver Fails With ORA-12154 While TNSNAMES.ORA Is Kept In Hidden Shared Folder (Doc ID 2594238.1)

Last updated on OCTOBER 26, 2019

Applies to:

Oracle Data Provider for .NET - Version 12.1.0.2 and later
Microsoft Windows x64 (64-bit)

Symptoms

ODP.Net managed gives "ORA-12154: TNS:could not resolve the connect identifier specified" when TNS_ADMIN (sqlnet.ora and tnsnames.ora) are placed on a hidden file share (one with $ at the end, e.g. \\localhost\tnsadmin$).

Steps:

1. Create a hidden folder in local computer or network driver and place the "tnsnames.ora" file in it.

Below link has concept("hidden share") to keep the tnsnames.ora file in hidden file:
https://answers.microsoft.com/en-us/windows/forum/all/how-to-create-a-hidden-share-in-a-network/1d2c75a3-5feb-48d4-9dbe-e2dba34ef6fd

7. From same command prompt open visual studio solution project which is saved eaelier for test connection.

8. Test it with 19c "Oracle.ManagedDataAccess" which will result in "ORA-12154" error.

9. Same code works fine with 12.2/18c managed as well as While connecting from sql*plus both 18c and 19c works fine with "hidden share" concept.

Changes

 For security purpose the TNS_ADMIN is kept in hidden file share.

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.