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 5.1.4

ENHANCEMENTS

• 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.*
• Support for result set holdability has been added to the driver.

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 | 5.1.4.00309
• 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
• The driver no longer registers the Statement Pool Monitor as a JMX MBean by
  default. To register the Statement Pool Monitor and manage statement pooling with
  standard JMX API calls, the new RegisterStatementPoolMonitorMBean connection
  property must be set to true. Refer to RegisterStatementPoolMonitorMBean for details.*

NOTES, KNOWN ISSUES, AND LIMITATIONS

• "Poor performing query" Error Message: Oracle Service Cloud returns a "Poor performing query" error when executing certain queries with the driver. This typically occurs when executing a query that requires the Oracle Service Cloud service to perform join operations on tables containing a large number of rows. We are currently working on a permanent solution to this problem; however, in the interim, you can work around this issue by doing the following:
  1. Configure the following connection properties to the values provided:
     • ConfigOptions: Value: (NamedIDBehavior=2)
       Note: In addition to specifying the recommended value, include any other key value pairs that you currently specify for ConfigOptions. These key value pairs should be specified in parentheses in a comma-separated list. For details, see "ConfigOptions" in the User's Guide.
     • CreateDB: Value: forceNew
       Note: Set CreateDB to forceNew for your initial connection. With this setting for the initial connection, NamedIDBehavior=2 takes effect and local map files are rebuilt to avoid "Poor performing query" errors. After the local map files have been rebuilt, CreateDB should be set to your preferred setting. We recommend setting CreateDB to notExist.
     • EnablePagingWithOrderByID: Value: true
       Note: This default value allows the driver to inject the Order By clause in the Select query.
  2. Connect to your Oracle Service Cloud instance. At connection, the driver deletes the current local map files and creates new files using the updated configuration option settings.
  3. Change the value of CreateDB to your preferred setting before your next connection. We recommend specifying a value of notExist.
  4. Test your settings by executing a query that previously returned the error. Based on the results, choose one of the following:
     • If you receive the "Poor performing query" error, proceed to the next step.
     • If your query is successfully returned, skip to the "Results" section.
  5. Tune the driver's fetching behavior. Using the WSFetchSize property, decrease the number of rows the driver attempts to fetch until the "Poor performing query" error is no longer returned. For optimal performance, configure WSFetchSize so that the driver returns the maximum number of rows possible without returning the error. For example, if you receive the error fetching 500 rows, but not 499 rows, set WSFetchSize=499 for maximum throughput. Be aware that decreasing the fetch size can increase the number of web service calls the driver makes to the Oracle Service Cloud service. If your query exceeds the statement call limit, increase the number of rows fetched using WSFetchSize or increase the statement call limit using the StatementCallLimit property to work around this issue.
     
     Notes:
     • You must disconnect and reconnect for changes to connection property values to take effect.
     • In the default setting, WSFetchSize=0, the driver uses the maximum page size allowed by the database to determine the number of rows it attempts to fetch for Oracle Service Cloud versions August 2014 or later. For versions earlier than August 2014, the driver attempts to fetch a maximum of 10,000 rows.
  Results: This configuration allows you to avoid the "Poor performing query" error in subsequent connections. If you begin receiving the error again, tune the WSFetchSize connection property according to the guidelines provided in step 4.
• CreatedTime and UpdatedTime Fields: Although the CreatedTime and UpdatedTime fields on custom objects map to the relational view, you cannot query against them unless you enable the fields within the Object Designer in the Oracle Service Cloud admin tool.
• ExtStatementPoolMBean Method: When calling the ExtStatementPoolMonitorMBean.getName() method, the driver should return a concatenation of the driver's name, the loginHost URL to which the Statement Pool Monitor is connected, and the MBean ID of the connection. The driver returns null in place of the loginHost URL.
• Invalid Schema Error: The driver returns an invalid schema error when creating a view using a two-part name in the view definition.
• DROP CACHE Statement: In some situations, executing a DROP CACHE statement will complete successfully without dropping the cache.
• Queries Against File Attachments: Queries against File attachments for sub-objects fail to retrieve the attachment data.
• Executing DataDirect Shell Script: For UNIX 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
• Performance Tuning Wizard: The Performance Tuning Wizard is not available with the Oracle Service Cloud driver. For information on tuning the driver for performance, see "Performance Considerations" in the USER'S GUIDE.
• Help System Issue: Internet Explorer with the Google Toolbar installed sometimes displays the following error when the browser is closed: "An error has occurred in the script on this page." This is a known issue with the Google Toolbar and has been reported to Google. When closing the driver's help system, this error may display.

Version 5.1.3

GA Release Features

• Supports SQL read-only access to data managed by Oracle Service Cloud
• Maps the Oracle Service Cloud data model to a set of relational tables and uses a client-side data cache for improved performance
• Supports the Oracle RightNow CX API
• Supports SSL encryption
• Supports statement pooling
• Supports connecting through a proxy server