Powered by Zoomin Software. For more details please contactZoomin

DataDirect JDBC ReadMe

Oracle Eloqua JDBC 6.0.0

  • Last Updated: May 8, 2026
  • 8 minute read
    • OpenAccess SDK
    • Documentation

     README
     Progress(R) DataDirect(R)
     Progress(R) DataDirect(R) for JDBC(TM) for Oracle Eloqua(TM) Driver
     Release 6.0.0
     February 2026


***********************************************************************
Copyright (C) 2026 Progress Software Corporation and/or its 
subsidiaries or affiliates. All Rights Reserved.

***********************************************************************


CONTENTS

Post-GA Product Announcements
Requirements
Installation directory
Data Source and Platform Support 
Changes since 6.0
Release 6.0 Features
Notes, known problems, and restrictions
Documentation
Installed files


     Post-GA Product Announcements
The readme files will no longer be updated with product announcements and new 
features after the General Availability (GA) of the product. For the latest 
updates and enhancements, please refer to the release notes 
(https://www.progress.com/datadirect-connectors/whats-new).


     Requirements

* A supported Java Virtual Machine (JVM) must be defined on your system path.

* The installer program requires a JVM that is Java SE 11 or higher, including
  Oracle JDK, OpenJDK, and IBM SDK (Java) distributions.
  
* The driver requires a JVM that is Java SE 8 or higher, including Oracle JDK,
  OpenJDK, and IBM SDK (Java) distributions.



     Installation directory

The default installation directory for the driver is:

* Windows:
  C:\Program Files\Progress\DataDirect\JDBC

* UNIX/Linux:
  /opt/Progress/DataDirect/JDBC
  Note: For UNIX/Linux, if you do not have access to "/opt", your user's
  directory should be used in place of this directory.


    Data Source and Platform Support

For the latest data source and platform support information, refer to the 
Product Compatibility Guide: 
https://docs.progress.com/bundle/datadirect-product-compatibility/resource/
datadirect-product-compatibility.pdf    


     Changes since 6.0

CVE-2022-41853 - Use of Externally-Controlled Input to Select Classes or Code
('Unsafe Reflection')
-----------------------------------------------------------------------------
Several Progress DataDirect JDBC drivers  utilized a version of HyperSQL
Database that was vulnerable to remote code execution described in
CVE-2022-41853. All impacted drivers have been patched to fix this
vulnerability. For details on impacted drivers and fixed versions, refer to
the following KB article:
https://community.progress.com/s/article/DataDirect-JDBC-Critical-Security-
Bulletin-November-2022-CVE-2022-41853
     
Documentation
-------------
Any product package made available after August 7, 2020 will not include the
HTML help system or user's guide PDF. The full documentation set, including
these items, is available from the Progress Information Hub:
https://docs.progress.com/category/datadirect-oracle-eloqua

While the product packages will not include these documentation items, the
installation Help directory will provide an HTML redirect for direct access
to the HTML help.

Note that all Progress DataDirect for JDBC documentation has been migrated to
the Progress Information Hub:
https://docs.progress.com/

Enhancements 
------------
* The driver has been enhanced to comply with FIPS standards for data
  encryption. As part of this enhancement, the driver was tested with
  FIPS 140-3 enabled using a Red Hat OpenJDK 21 on a Red Hat Universal Base
  Image 9 instance.


* The driver has been enhanced to use proxy server settings defined in the JVM 
  system properties by default. If no proxy settings are defined in the 
  connection string or data source, the driver will attempt to use the values 
  of the http.proxyHost and http.proxyPort JVM system properties to connect to 
  the database.

* The driver has been enhanced to include timestamp in the Spy and JDBC packet
  logs by default. If required, you can disable the timestamp logging by 
  specifying the following at connection: For Spy logs, set 
  spyAttributes=(log=(file)Spy.log;timestamp=no) and for JDBC packet logs,
  set ddtdbg.ProtocolTraceShowTime=false.

* Interactive SQL for JDBC (JDBCISQL) is now installed with the product. 
  JDBCISQL is a command-line interface that supports connecting your driver
  to a data source, executing SQL statements and retrieving results in a 
  terminal. This tool provides a method to quickly test your drivers in an 
  environment that does not support GUIs.


Changed Behavior 
----------------
* The connection property SpyAttributes has been updated to exclude the 
  attribute load=classname, which was previously used to load the driver 
  specified by the given class name. See SpyAttributes for details.
  
* The installer program now requires you to install a JRE that is Java SE 11 or
  higher before running the installer. In earlier versions, the JRE used by the
  installer program was included in the product. However, to avoid potential
  security vulnerabilities, the installer program no longer includes a JRE.
  Instead, the installer program uses the JRE in your environment to allow for
  the most secure version of a JRE to be used.
 
  Note: This change does not affect the JVM requirements for the driver. For the latest 
  driver requirements, refer to the Product Compatibility Guide:
  https://docs.progress.com/bundle/datadirect-product-compatibility/resource/
  datadirect-product-compatibility.pdf


* Java SE 7 has reached the end of its product life cycle and will no longer   
  receive generally available security updates. As a result, the drivers will no 
  longer support JVMs that are version Java SE 7 or earlier. Support for 
  distributed versions of Java SE 7 and earlier will also end, including
  IBM SDK (Java Edition). 


     Release 6.0 Features

The driver supports standard supports SQL read-write access to Oracle Eloqua.
To support SQL access to Oracle Eloqua, the driver creates a relational map of
the Oracle Eloqua data model and translates SQL statements provided by the
application to Oracle Eloqua queries and web service calls. The driver
optimizes performance when executing joins by leveraging data relationships
among Oracle Eloqua objects to minimize the amount of data that needs to be
fetched over the network. The driver recognizes the relationships among
standard objects and custom objects and can access and update each.
Relationships among objects can be reported with JDBC the metadata methods.

* The driver supports all JDBC Core functions.

* The driver supports the core SQL-92 grammar.

* The driver supports connecting through a proxy server.

* The driver uses a combination of REST and BULK APIs for optimized fetch
  operations.
  
* The driver supports retrieving LONGVARCHAR data, using JDBC methods designed
  for Character Large Object (CLOB) data.

* The driver supports timeout functionality.

* The driver supports the following data types:
  - ARRAY         maps to VARCHAR
  - BOOLEAN       maps to BOOLEAN
  - DATETIME      maps to TIMESTAMP
  - DECIMAL       maps to DECIMAL
  - DURATION      maps to VARCHAR
  - INTEGER       maps to INTEGER
  - LARGETEXT     maps to LONGVARCHAR
  - LONG          maps to BIGINT
  - TEXT          maps to VARCHAR
  - URL           maps to VARCHAR


     Notes, known problems, and restrictions

The following are notes, known problems, and restrictions with the Oracle
Eloqua driver.

Update and Delete
-----------------
Only one record at a time can be updated or deleted. Therefore, the number of
APIs executed depends on the number of rows that get updated or deleted by
the query plus the number of API calls required to fetch the IDs for those
records.

Text field metadata
-------------------
Lengths of certain text fields are reported as higher than the actual lengths.

REST API issues
----------------
We are currently working with Oracle to resolve the following issues.

* AND operators that involve different columns are optimized. In other cases,
  the queries are only partially optimized.

* OR operators on the same column are optimized. In other cases, the queries
  are completely post-processed.
* The data store is not able to insert or update the NULL value to any field
  explicitly.

* The data store is unable to update few fields. They are always reported as
  NULL after update.

* Oracle Eloqua uses a double colon (::) as an internal delimiter for
  multivalued Select fields. Hence when a value with the semi-colon character
  (;) is inserted or updated into a multivalued Select field, the semicolon
  character gets converted into the double colon character.

* Query SELECT count (*) from template returns incorrect results.

* Oracle Eloqua APIs do not populate the correct values in CreatedBy and
  UpdatedBy fields. Instead of user names, they contain a Timestamp value.

* Only equality filters on id fields are optimized. All other filter
  conditions are not working correctly with Oracle Eloqua APIs and the data
  store is doing post-processing for such filters.

* Filters on Non-ID Integer fields and Boolean fields are not working
  correctly. Hence the driver needs to post-process all these queries.

* The data store does not distinguish between NULL and empty string.
  Therefore, null fields are often reported back as empty strings.

* Values with special characters such as curly braces ({,}), back slash (\),
  colon (:), slash star (/*) and star slash (*/) are not supported in where
  clause filter value.

Executing DataDirect shell script
---------------------------------
For UNIX/Linux users: If you receive an error message when executing any
DataDirect for JDBC shell script, make sure that the file has EXECUTE
permission. To do this, use the chmod command. For example, to grant EXECUTE
permission to the testforjdbc.sh file, change to the directory containing
testforjdbc.sh and enter: chmod +x testforjdbc.sh 

Scroll sensitive requests
-------------------------
When attempting to create an updatable, scroll-sensitive result set for a
query that contains an expression as one of the columns, the driver cannot
satisfy the scroll-sensitive request. The driver downgrades the type of the
result returned to scroll-insensitive.

ResultSet methods getTimestamp(), getDate(), and getTime()
----------------------------------------------------------
The ResultSet methods getTimestamp(), getDate(), and getTime() return
references to mutable objects. If the object reference returned from any of
these methods is modified, re-fetching the column using the same method
returns the modified value. The value is only modified in memory; the database
value is not modified.


     Documentation	 	 

PROGRESS DATADIRECT FOR JDBC FOR ORACLE ELOQUA DOCUMENTATION SET
----------------------------------------------------------------
The driver documentation set is available from the Progress Information Hub:

https://docs.progress.com/category/datadirect-oracle-eloqua

You can access the online help system directly via the HTML redirect in the
installation Help directory.


     Installed Files

When you extract the contents of the installation download package to your
installer directory, you will notice the following files that are required to
install the driver:

*  Windows:
   - PROGRESS_DATADIRECT_JDBC_INSTALL.exe
   - DriverModules
     - PROGRESS_DATADIRECT_JDBC_ELOQUA_6.0.0_INSTALL.iam.zip
     - PROGRESS_DATADIRECT_JDBC_COMMON_6.0.0_INSTALL.iam.zip

*  Non-Windows:
   - PROGRESS_DATADIRECT_JDBC_INSTALL.jar
   - DriverModules
     - PROGRESS_DATADIRECT_JDBC_ELOQUA_6.0.0_INSTALL.iam.zip
     - PROGRESS_DATADIRECT_JDBC_COMMON_6.0.0_INSTALL.iam.zip

When you install the driver, the installer creates the following directories and
files in the product installation directory in the default installation
directory or in an installation directory you specify, represented by
INSTALL_DIR.

INSTALL_DIR/:
-------------
LicenseTool.jar            Product license file manager

ddprocinfo.exe             Windows executable to start the Processor Information
                           Utility

ddprocinfo                 UNIX/Linux script to start the Processor Information
                           Utility


INSTALL_DIR/Examples/Connector/:
--------------------------------
ConnectorSample.ear        J2EE Application Enterprise Archive file containing
                           the ConnectorSample application 

connectorsample.htm        USING DATADIRECT CONNECT FOR JDBC RESOURCE ADAPTERS
                           document

graphics/*.*               Images referenced by the USING DATADIRECT CONNECT FOR
                           JDBC RESOURCE ADAPTERS document

src/ConnectorSample.jsp    Source for the JavaServer Page used to access the
                           ConnectorSample application

src/connectorsample/ConnectorSample.java     
                           Java source file defining the remote interface for
                           the ConnectorSample EJB

src/connectorsample/ConnectorSampleBean.java  
                           Java source file defining the home interface for the
                           ConnectorSample EJB

src/connectorsample/ConnectorSampleHome.java  
                           Java source file containing the implementation for
                           the ConnectorSample EJB


INSTALL_DIR/Examples/JNDI/:
---------------------------
JNDI_FILESYSTEM_Example.java
                           Example Java(TM) source file

JNDI_LDAP_Example.java     Example Java source file


INSTALL_DIR/Examples/OracleEloquaSamples/:
------------------------------------------
buildsamples.bat           Batch file to build the Eloqua example

buildsamples.sh            Shell script to build the Eloqua example

runeloquaconnectsample.bat
                           Batch file to run the Eloqua example

runeloquaconnectsample.sh
                           Shell script to run the Eloqua example

bin/com/ddtek/jdbc/samples/EloquaConnectSample.class
                           Java example class

bin/com/ddtek/jdbc/samples/SampleException.class
                           Java example class

src/com/ddtek/jdbc/samples/EloquaConnectSample.java
                           Java source example


INSTALL_DIR/help/: 
------------------
*.html                     HTML redirects to driver help systems


INSTALL_DIR/install/: 
---------------------
.psc_dd_inst_reg.xml       Support file for the installation logs

logs/*.*                   Log file generated upon installing or uninstalling


INSTALL_DIR/jdbcisql/:
----------------------
jdbcisql.bat               Batch file to start JDBC iSQL

jdbcisql.jar               Java program to start JDBC iSQL

jdbcisql.sh                Shell script to start JDBC iSQL


INSTALL_DIR/lib/60/:
--------------------
eloqua.jar                 Oracle Eloqua Driver and DataSource classes


INSTALL_DIR/NOTICES/:
---------------------
JDBC for Oracle Eloqua v6.0 notices.txt
                           Third party agreement information


INSTALL_DIR/pool manager/:
--------------------------
pool.jar                   All DataDirect Connection Pool Manager classes


INSTALL_DIR/READMES/:
---------------------
JDBC for Oracle Eloqua v6.0 readme.txt
                           This file


INSTALL_DIR/testforjdbc/:
-------------------------
Config.txt                 Configuration file for DataDirect Test

ddlogging.properties       Logging properties file

testforjdbc.bat            Batch file to start DataDirect Test

testforjdbc.sh             Shell script to start DataDirect Test

lib/testforjdbc.jar        DataDirect Test classes


INSTALL_DIR/uninstall/:
-----------------------
.com.zerog.registry.xml    Support file for the uninstaller

.psc_dd_uninst_reg.xml     Support file for the uninstaller

InstallScript.iap_xml      Support file for the uninstaller

installvariables.properties
                           Support file for the Windows uninstaller

Uninstall_JDBC.exe         Windows uninstaller

Uninstall_JDBC.lax         Support file for the Windows uninstaller

uninstaller.jar            Java uninstaller

eloqua/*.*                 Support files for the uninstaller

resource/*.*               Resource files for the Windows uninstaller


February 2026
================
End of README

TitleResults for “How to create a CRG?”Also Available inAlert