Access Oracle Eloqua Reporting Data as a Remote Oracle Database

The Oracle Database Gateway for ODBC and Heterogeneous Services technology enable you to connect to ODBC data sources as remote Oracle databases. This article shows how to use the CData ODBC Driver for Oracle Eloqua Reporting to create a database link from Oracle Eloqua Reporting to Oracle and to query Oracle Eloqua Reporting data through the SQL*Plus tool. You can also create the database link and execute queries from SQL Developer.

Connect to Oracle Eloqua Reporting as an ODBC Data Source

Information for connecting to Oracle Eloqua Reporting follows, along with different instructions for configuring a DSN in Windows and Linux environments.

Oracle Eloqua Reporting supports the following authentication methods:

• Basic authentication (User and Password)
• OAuth 2.0 code grant flow
• OAuth 2.0 password grant flow

Basic Authentication (User and Password)

To perform authentication with a user and password, specify these properties:

• AuthScheme: Basic.
• Company: The company name associated with your Oracle Eloqua Reporting account.
• User: Your login account name.
• Password: Your login password.

OAuth Authentication (Code Grant Flow)

To authenticate with the OAuth code grant flow, you must set AuthScheme to OAuth and create a custom OAuth application. For information about how to create a custom OAuth application, see the Help documentation.

Then set the following properties:

• InitiateOAuth: GETANDREFRESH. Used to automatically get and refresh the OAuthAccessToken.
• OAuthClientId: The client Id assigned when you registered your application.
• OAuthClientSecret: The client secret that was assigned when you registered your application.
• CallbackURL: The redirect URI that was defined when you registered your application.

When you connect, the driver opens Oracle Eloqua Reporting's OAuth endpoint in your default browser. Log in and grant permissions to the application. When the access token expires, the driver refreshes it automatically.

OAuth Authentication (Password Grant Flow)

With the OAuth password grant flow, you can use your OAuth application's credentials alongside your user credentials to authenticate without the need to grant permission manually via a browser prompt. You must create an OAuth app (see the Help documentation) to use this authentication method.

Set the following properties:

• AuthScheme: OAuthPassword
• Company: The company's unique identifier.
• User: Your login account name.
• Password: Your login password.
• OAuthClientId: The client Id assigned when you registered your custom OAuth application.
• OAuthClientSecret: The client secret assigned when you registered your custom OAuth application.

Windows

If you have not already, first specify connection properties in an ODBC DSN (data source name). This is the last step of the driver installation. You can use the Microsoft ODBC Data Source Administrator to create and configure ODBC DSNs.

Note: If you need to modify the DSN or create other Oracle Eloqua Reporting DSNs, you must use a system DSN and the bitness of the DSN must match your Oracle system. You can access and create 32-bit DSNs on a 64-bit system by opening the 32-bit ODBC Data Source Administrator from C:\Windows\SysWOW64\odbcad32.exe.

Linux

If you are installing the CData ODBC Driver for Oracle Eloqua Reporting in a Linux environment, the driver installation predefines a system DSN. You can modify the DSN by editing the system data sources file (/etc/odbc.ini) and defining the required connection properties.

/etc/odbc.ini

[CData OracleEloquaReporting Source]
Driver = CData ODBC Driver for Oracle Eloqua Reporting
Description = My Description
AuthScheme = Basic
User = user
Password = password
Company = MyCompany

For specific information on using these configuration files, please refer to the help documentation (installed and found online).

Set Connection Properties for Compatibility with Oracle

The driver provides several connection properties that streamline accessing Oracle Eloqua Reporting data just as you would an Oracle database. Set the following properties when working with Oracle Eloqua Reporting data in SQL*Plus and SQL Developer. For compatibility with Oracle, you will need to set the following connection properties, in addition to authentication and other required connection properties.

• MapToWVarchar=False

  Set this property to map string data types to SQL_VARCHAR instead of SQL_WVARCHAR. By default, the driver uses SQL_WVARCHAR to accommodate various international character sets. You can use this property to avoid the ORA-28528 Heterogeneous Services data type conversion error when the Unicode type is returned.

• MaximumColumnSize=4000

  Set this property to restrict the maximum column size to 4000 characters.

• IncludeDualTable=True

  Set this property to mock the Oracle DUAL table. SQL Developer uses this table to test the connection.

Linux Configuration

In Linux environments, Oracle uses UTF-8 to communicate with the unixODBC Driver manager, whereas the default driver encoding is UTF-16. To resolve this, open the file /opt/cdata/cdata-driver-for-oracleeloquareporting/lib/cdata.odbc.oracleeloquareporting.ini in a text editor and set the encoding.

cdata.odbc.oracleeloquareporting.ini

[Driver]
DriverManagerEncoding = UTF-8

Configure the ODBC Gateway, Oracle Net, and Oracle Database

Follow the procedure below to set up an ODBC gateway to Oracle Eloqua Reporting data that enables you to query live Oracle Eloqua Reporting data as an Oracle database.

1. Create the file initmyeloquareportingdb.ora in the folder oracle-home-directory/hs/admin and add the following setting:

   initmyeloquareportingdb.ora

   HS_FDS_CONNECT_INFO = "CData OracleEloquaReporting Sys"

2. Add an entry to the listener.ora file. This file is located in oracle-home-directory/NETWORK/admin.

   If you are using the Database Gateway for ODBC, your listener.ora needs to have a SID_LIST_LISTENER entry that resembles the following:

   listener.ora

   SID_LIST_LISTENER =
    (SID_LIST =
    (SID_DESC =
    (SID_NAME = myeloquareportingdb)
    (ORACLE_HOME = your-oracle-home)
    (PROGRAM = dg4odbc)
    )
    )
   

   If you are using Heterogeneous Services, your listener.ora needs to have a SID_LIST_LISTENER entry that resembles the following:

   listener.ora

   SID_LIST_LISTENER =
    (SID_LIST =
    (SID_DESC =
    (SID_NAME = myeloquareportingdb)
    (ORACLE_HOME = your-oracle-home)
    (PROGRAM = hsodbc)
    )
    )
   

3. Add the connect descriptor below in tnsnames.ora, located in oracle-home-directory/NETWORK/admin:

   tnsnames.ora

   myeloquareportingdb =
    (DESCRIPTION=
    (ADDRESS=(PROTOCOL=tcp)(HOST=localhost)(PORT=1521))
    (CONNECT_DATA=(SID=myeloquareportingdb))
    (HS=OK)
    ) 
   

4. Restart the listener.

5. Test the configuration with the following command:

   tnsping myeloquareportingdb

6. Open SQL*Plus and create the database link with the command below:

   CREATE DATABASE LINK myeloquareportingdb CONNECT TO "user" IDENTIFIED BY "password" USING 'myeloquareportingdb';

You can now execute queries in SQL*Plus like the one below (note the double quotation marks around the table name):

SELECT * from ""@myeloquareportingdb WHERE = '';