Important Notice: Our web hosting provider recently started charging us for additional visits, which was unexpected. In response, we're seeking donations. Depending on the situation, we may explore different monetization options for our Community and Expert Contributors. It's crucial to provide more returns for their expertise and offer more Expert Validated Answers or AI Validated Answers. Learn more about our hosting issue here.

What is the difference between using generic connectivity and ODBC drivers to connect to non-Oracle databases?

April 26, 2017Connect connectivity databases difference Drivers generic non-Oracle ODBC

0

Posted

What is the difference between using generic connectivity and ODBC drivers to connect to non-Oracle databases?

1 Answer

0

Posted

In previous versions of Discoverer, users could connect to non-Oracle databases using ODBC drivers. The major difference between using ODBC drivers to connect to a non-Oracle database and using the Oracle database generic connectivity feature is the location of the EUL, as follows: with ODBC drivers, the EUL is stored in the non-Oracle database with generic connectivity, the EUL is stored in the Oracle database Figure 22-1 EUL location using ODBC drivers versus using generic connectivity Text description of the illustration hdsmigr.gif The above diagram illustrates the following: when Discoverer connects to a non-Oracle database using ODBC drivers, both the EUL and the data reside on the non-Oracle database when Discoverer connects to a non-Oracle database using generic connectivity, the data continues to reside on the non-Oracle database but the EUL must be located on the Oracle database Discoverer no longer supports the use of native ODBC drivers to connect to non-Oracle databases. Y