When you enter an Oracle net service name (alias) in the Server field of the Oracle connector. The alias is resolved by LDAP directory naming (ldap.ora, plus NAMES.DIRECTORY_PATH=(LDAP, ...) in sqlnet.ora). The connection fails with one of these errors:
tnsping.tnsnames.ora connects without problems.jprotocolserver) shows java.net.UnknownHostException: No such host is known (<alias>). The connection string uses the alias as the host name:ojdbc8.jar, ojdbc11.jar)ldap.oratnsnames.ora, in the folder set by oracle.net.tns_admin in the oracle.properties file.ldap.ora or NAMES.DIRECTORY_PATH for the Oracle connector.tnsping do read those files. This is why the alias works there and not in Tableau.tnsnames.ora, Tableau treats the Server value as a host name. DNS can't resolve it, so you see UnknownHostException or ORA-17868.ldap.ora file your Oracle tools use (usually in <ORACLE_HOME>/network/admin or your TNS_ADMIN folder). It looks like this:
Attempting to contact, for example:(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=db01.example.com)(PORT=1521))(CONNECT_DATA=(SERVICE_NAME=sales.example.com)))tnsnames.ora file:SALES =tnsnames.ora using oracle.properties, as described in Setting an Oracle Connection to Use TNSNames.ora.SALES) in Server.tnsnames.ora is a static copy. If the DBA changes the entry in LDAP, update tnsnames.ora too.db01.example.comsales.example.com1521tnsping output in Option 2.
ldap.ora and sqlnet.ora. Tableau's Oracle connector uses the JDBC Thin driver, which doesn't use those files for name lookups.tnsnames.ora from that folder.ldap.ora doesn't contain aliases. It only says where the LDAP server is (DIRECTORY_SERVERS) and where to search (DEFAULT_ADMIN_CONTEXT). The alias entries are stored in the LDAP directory itself.005461848

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.