"TNS could not resolve the connect identifier specified" error, user not on main MIT campus, VPN not a viable option

ORA-12154: TNS:could not resolve the connect identifier specified

ORA-12154: TNS:could not resolve service name

For a simpler solution [ "TNS could not resolve connect identifier specified", "...could not resolve service name"]

Step One: If user is truly off campus

[ "TNS could not resolve connect identifier specified", "...could not resolve service name"] instructs off-campus users to connect to the VPN before connecting to the Data Warehouse.

Step Two: If user is on a DLC subnet

Users in DLC's which are not on the 18.x.x.x netowrk may have reasons that make running the VPN not a viable solution. For example, connections to DLC servers may require an IP address specific to the departmental subnet. This article provides two possible solutions for those users.

Option One: Configuration for Oracle LDAP servers

• We may be able to work with O&I to configure the Oracle LDAP servers to allow connections for the DLC's subnet. For example, O&I has added the PSFC IP range to the firewall acl for tnsnames.mit.edu.

Option Two:

Another possible workaround, as a temporary solution, is to use a local tnsnames file. The instructions below are complicated and clients may need assistance from local technical support to accomplish them.

1. Use Notepad to create on the Desktop a file called tnsnames.ora
   Note: The extension should be .ora, not .txt. Hide extensions for known file types will need to be turned off in order to accomplish this.
2. Copy and paste the following into that file:

   # TNSNAMES.ORA file for MIT community access to the Data Warehouse
   #
   #
   # NOTE: This file should be used on Windows PC's with the appropriate SQLNET.ORA file.
   
   
   warehouse =
     (DESCRIPTION =
       (ADDRESS_LIST =
         (ADDRESS = (PROTOCOL = TCP)(HOST = warehouse.mit.edu)(PORT = 1521))
       )
       (CONNECT_DATA = (SID = DWRHS))
     )
   

3. Move tnsnames.ora to C:\oracle\product\11.2.0\client\network\admin
4. Try again to connect to the Data Warehouse via BrioQuery.