An asterisk (*) indicates support that was added in a hotfix or software patch subsequent to a release.

Refer to the following resources for additional information:

• Product Compatibility Guide: Provides the latest data source and platform support information. 
• Fixes: Describes the issues resolved since general availability.  

Version 6.0.0

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. Refer to FIPS (Federal Information Processing Standard) for details.*
  Available: 1/31/2025 | 6.0.0.001222
• 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. Refer to SpyAttributes for details.*
• 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 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.
  Available: 7/3/2024

NOTES, KNOWN ISSUES, AND LIMITATIONS

• 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.

Features

• Supports SQL read-write access to Oracle Eloqua. Refer to Supported SQL functionality for details.
  
• Supports JDBC core functions. Refer to JDBC Support in the Progress DataDirect for JDBC Drivers Reference.
  
• Supports Oracle Eloqua data types. Refer to Data types and getTypeInfo() for details.
  
• Supports HTTP proxy. Refer to Proxy server support support for details.
  
• Uses a combination of REST and Bulk APIs for optimized fetch operations. Refer to Bulk operations for details.
  
• Supports retrieving LONGVARCHAR data, using JDBC methods designed for Character Large Object (CLOB) data. Refer to Large object (LOB) support for details.
  
• Supports timeout functionality. Refer to Timeouts for details.