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.001065
• 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. If a log file name does not include the .log extension, the driver automatically appends it.*
  Available: 10/24/2025 | 6.0.0.001316
• The driver has been updated to remove all sensitive values from the string returned by calling getURL(). You might be impacted if your applications or tests expect these values when calling the function.*
• 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

• Limitations of Proxy Server Support: The driver does not currently support connecting through a proxy server when authentication is enabled.
• Filter conditions: Currently, passing filter conditions only works for simple, single column conditions. If there are multiple filters with 'AND' and 'OR', only partial or no filters are passed to Oracle Sales Cloud.
• String and Date field metadata: Oracle Sales Cloud reports the data type of String and Date fields as String. The driver treats these fields as String values. However, when filter conditions are passed to Oracle Sales Cloud, Oracle Sales Cloud distinguishes between the actual data types and apply Date specific comparisons to Date fields. Therefore, query results can differ depending on whether filters have been passed down to Oracle Sales Cloud or processed by the SQL engine embedded in the driver.
• Comparison operators: There appears to be a limitation with the Oracle Sales Cloud REST API concerning the >=, <=, and != comparison operators when querying String fields. Therefore, the driver has not been optimized to pass these comparison operators to Oracle Sales Cloud. We are working with Oracle on this issue.
• Filter operations on Boolean fields: There appears to be a limitation with the Oracle Sales Cloud REST API concerning queries with filter operations on Boolean fields. Therefore, the driver has not been optimized to pass filter operations on Boolean fields to Oracle Sales Cloud. We are working with Oracle on this issue.
• Attachment type: The driver currently reports Attachment type fields in the metadata but does not support retrieving data for these fields. These fields are set to NULL.
• Parent-child join queries: Join queries between parent and child tables are not supported.
• Parent table with composite primary key: Queries on child tables whose parent has a composite primary key are not supported. For example, the children of ACTIVITIES_ACTIVITYCONTACT and LEADS_PRODUCTS are not accessible.
• Relationship object queries: Queries on the children of relationship objects are not supported. For example, the children of ACCOUNTS_RELATIONSHIP, CONTACTS_RELATIONSHIP, and HOUSEHOLDS_RELATIONSHIP are not accessible.
• Grandchildren tables with OR clause filter: Queries on grandchildren with multiple sets of Parent IDs and Grand Parent IDs used in an OR clause are not supported. For example, the following query is not supported:

  select * from ACCOUNTS_ADDRESS_ADDRESSPURPOSE
     where (ACCOUNTS_PARTYNUMBER = 'OSC_12343' AND
            ACCOUNTS_ADDRESS_ADDRESSNUMBER = 'AUNA-2XZKGH')
        or (ACCOUNTS_PARTYNUMBER = 'OSC_12344' AND
            ACCOUNTS_ADDRESS_ADDRESSNUMBER = 'AUNA-2YZKGH')

• Document object queries: When querying documented objects like "CATALOGPRODUCTITEMS" and "CATEGORYPRODUCTITEMS", no more than 500 records are returned, even when more records may be present. This behavior is also seen with some custom objects. We are currently working with Oracle support to resolve this issue.
• OPPORTUNITIES_CHILDREVENUE_PRODUCTS or LEADS_PRODUCTGROUPS queries: A query on OPPORTUNITIES_CHILDREVENUE_PRODUCTS or LEADS_PRODUCTGROUPS with a filter on the primary key column returns 0 records even when more records are present. We are currently working with Oracle support to resolve this issue.
• Subqueries with more than 100 records: Queries that contain subqueries returning more than 100 records are not supported. For example, the following query is not supported:

  select * from ACCOUNTS_ADDRESS
  where ACCOUNTS_PARTYNUMBER
  in (select top 101 PARTYNUMBER from ACCOUNTS)

• Creating custom objects: When you create custom objects, your Oracle Sales Cloud administrator must enable these objects for REST API access through Application Composer. Otherwise, you will not be able to query against these custom objects.
• 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

Features

• Supports SQL read access to Oracle Sales Cloud
• Supports JDBC core functions
• Supports Oracle Sales Cloud data types
• Supports HTTP proxy
• Supports timeout functionality