The ODBC Manager is a tool for configuring drivers and creating and managing
DSNs. The tool is optional because you can also create DSNs manually by editing
the appropriate odbc.ini file.
Follow these steps to configure the ODBC Driver on Mac OS.
You can create User DSNs (only accessible by the user who created it on the
workstation) or System DSNs (accessible by any user signed in to the workstation).
Get the host name for the SQL Endpoint to connnect to.
Open the Details Page for the SQL Endpoint when it's active.
Select Drivers.
Under ODBC driver, select Show
Details. A pop-up appears.
Select Show on the Host name string. The
full Host name is displayed.
Select Copy on the Host name string. The
full Host name is copied to the clipboard.
Save the Host name for later use.
(Optional)
Create a DSN using the ODBC Manager.
Start ODBC Manager.
Select User DSN or System DSN as appropriate.
Select Add.
Select Simba OCI Spark ODBC Driver.
Select OK.
Enter the name of the DSN, for example, Data Flow SQL
Endpoint and, optionally, add a description.
Create a Keyword Value pair for each DSN parameter.
Select Add to create a Keyword Value pair.
Select Keyword and replace it with the
parameter name.
Select Value and replace it with the value for
the parameter.
Repeat steps g to j for each parameter.
Add the connection authentication details:
For connecting to a SQL Endpoint using an API signing key not at
the default location ~/.oci/config, add the
parameter:
OCIConfigFile=ConfigFileLocation
where ConfigFileLocation is the absolute
path to the OCI
configuration file to use with the
connection.
Optionally, set the
OCIProfile field to the name of
the OCI profile
in the configuration file to use with the connection:
OCIProfile=<profile_to_use>
If no profile is specified, the connector try to use the
profile named DEFAULT:
OCIProfile=<profile_to_use>
For connecting to a SQL Endpoint using a token (through the
browser), omit the OCIConfigFile parameter from
the DSN configuration.
Select OK to create the DSN.
Note
If you create the first user or system DSN for the ODBC driver, the ODBC
Manager creates the odbc.ini file in the corresponding
directory for the type of DSN created. If you create more DSNs, the ODBC
Manager adds entries for each DSN to the existing odbc.ini
file. The odbc.ini file is under the directory
~/Library/ODBC for User DSNs and
/Library/ODBC for System DSNs.
(Optional)
Create a DSN by adding an entry to odbc.ini.
If a User DSN or a system DSN has already been created for the driver, add the
new entry to the existing odbc.ini file. If creating the first
DSN for the driver, manually create the odbc.ini file and add
the entry to the file.
If creating the first DSN in the empty odbc.ini file,
create a section for ODBC Data Sources (for the first time only), by
adding the following line to the odbc.ini file:
[ODBC Data Sources]
For each DSN, specify the following:
Under [ODBC Data Sources] specify the DSN name
and ODBC driver name (which is Simba OCI Spark ODBC
Driver), in the form, <dsn_name> =
<driver_name>. For example:
[ODBC Data Sources]dsn_name = Simba OCI Spark ODBC Driver
Create a section for DSN configuration, by adding
[dsn_name] in a new line at the end of the file.
[dsn_name]
Under the created DSN Section specify the directory path of the
driver file, in the
form:
Provide the connection parameters such as host, and config
file. Those connection parameters you add to the DSN don't
need to be specified in the ODBC connect string.
For connecting to SQL Endpoint using an API signing
key (not at the default location of
~/.oci/config), add the
parameter:
OCIConfigFile=ConfigFileLocation
where ConfigFileLocation is the
absolute path to the OCI
configuration file to use for the
connection.
Optionally, set the
OCIProfile field to the name of
the OCI profile in the config file to use for the
connection. If no profile is specified, the
connector tries to use the profile named,
DEFAULT:
OCIProfile=PROFILE_TO_USE
To connect to a SQL Endpoint using a token
(browser-based), you can omit the
OCIConfigFile parameter from the
DSN configuration.
Any other parameters are specified in the form of
<parameter_name> = <value>. The
following example shows an odbc.ini file that
configures the data sources using the API
key:
[ODBC Data Sources]
Data Flow SQL Endpoint = Simba OCI Spark ODBC Driver
[Data Flow SQL Endpoint]
Driver = /Library/simba/ocispark/lib/universal/libsparkodbc_sbu.dylib
Description = Description of the connection
Host = amaaaaaaezym32iajmhpmxybehc7plnvpxsmjhleiav37x5rm7pjx476ewqa.interactive.dataflowclusters.us-ashburn-1.oci.oc-test.com
OCIConfigFile = /Users/username/.oci/config
OCIProfile = OCIProfileToUse
OCIIgnoreDriverNoPrompt = 1
Confirm that path of the OCI
configuration file to use the API signing key for authentication is
correct.
Validate the private key file path in the configuration.
Downloading and Installing the ODBC Driver on Windows 🔗
Follow these steps to download and install an ODBC driver to use with Tableau on
Windows/
Download the Windows ODBC driver from .
In the global search bar, search for Data Flow and
select Data Flow Service.
Select SQL Endpoints in the leftmost side
navigation.
Select any SQL Endpoint from the list. The details page for that SQL
Endpoint is displayed.
Under Connect, select
Drivers.
Under ODBC, select Download ODBC driver.
Select Windows. The download begins.
When the download completes, extract the downloaded zip file.
Extract the .zip file.
Double-click the 32-bit installer, Simba OCI Spark 2.6
32-bit.msi, if the system is 32-bit, or double-click the 64-bit
installer , Simba OCI Spark 2.6 64-bit.msi, if the system is
64-bit.
Select Next.
Accept the terms of the License Agreement.
Select Next.
(Optional)
To change the install directory from the default:
Select Change....
Browse to the required directory.
Select OK.
To accept the install directory, select Next.
Select Install.
When the installation completes, select Finish.
Configuring the ODBC Driver on Windows 🔗
Follow these steps to configure the ODBC Driver on Windows.
You can create User DSNs (only accessible by the user who created it on the
workstation) or System DSNs (accessible by any user signed in to the workstation).
Get the host name for the SQL Endpoint to connnect to.
Open the Details Page for the SQL Endpoint when it's active.
Select Drivers.
Under ODBC driver, select Show
Details. A pop-up appears.
Select Show on the Host name string. The
full Host name is displayed.
Select Copy on the Host name string. The
full Host name is copied to the clipboard.
Save the Host name for later use.
Create a DSN.
Open the ODBC Data Sources App.
Select User DSN or System DSN as appropriate.
Select Add.
Select Simba OCI Spark ODBC Driver.
Select Finish.
Enter the name of the DSN, for example, Data Flow SQL
Endpoint and, optionally, add a description.
For authentication, you can use an API signing key to connect to a
SQL Endpoint, or you can use a token (browser-based) to connect to a
SQL Endpoint.
To use an API signing key
Set OCI Config File to
the absolute path to the OCI
configuration file to use for the connection.
Optionally, set the OCI
Profile field to the name of the OCI
profile to use for the connection. If no profile
is specified, the connector tries to use the
profile named DEFAULT.
Check Ignore
SQL_DRIVER_NOPROMPT.
Select OK to save the
settings.
To use a token (browser-based)
You can opt not to set up DFI Options entirely and only
test the DSN (step iv), or select DFI
Options and continue with the following steps:
Set the OCI Config File
field to a path that doesn't contain an OCI
configuration file to use token-based
authentication.
To display a web browser used to complete the
token-based authentication flow even when
SQL_DRIVER_NOPROMPT is enabled,
check Ignore SQL_
DRIVER_NOPROMPT.
Select OK to save the
settings.
To test the DSN, select
Test.
Select OK to create the DSN.
Connecting Tableau to a Data Flow SQL Endpoint Using
ODBC 🔗
Follow these steps to connect Tableau to a Data Flow
SQL Endpoint Using ODBC.
Open Tableau.
Select Other Databases (ODBC).
A new window opens.
Check DSN.
Select the DSN, Data Flow SQL Endpoint, from the list.
All the required connection parameters are automatically populated.