These release notes provide enhancements, changed behavior, and resolved issues. When applicable, a component-specific version number is provided for the On-Premises Connector, ODBC driver, or JDBC driver.
The product version number can be obtained from the Hybrid Data Pipeline Web UI by selecting About from the help dropdown.
For On-Premises Connectors, administrators can obtain version information using the Administrator Connectors API. See Obtaining information about On-Premises Connectors for details. In addition, version information can be obtained by opening the On-Premises Connector Configuration Tool and clicking the Version tab.
The JDBC driver version number can be obtained (1) by calling the DatabaseMetaData.getDriverVersion() method or (2) by executing the following command from the driver installation directory:
java -cp ddhybrid.jar com.ddtek.jdbc.ddhybrid.DDHybridDriver.
For the ODBC driver, see Driver version string for details on obtaining the driver version number.
Note: For the latest data source and platform support information, refer to the Product Compatibility Guide.
Log management capabilities have been enhanced. Administrators may now specify a centralized location for Hybrid Data Pipeline logs. In addition, administrators may set logging levels for system services, including the web UI, the data access service, the notification server, and the Apache Tomcat server. For details, refer to Log management.
For OData Version 4, Hybrid Data Pipeline now supports long binary and long character types up to 1 MB. Supported long binary types include BLOB and LONGVARBINARY. Supported long character types include CLOB, LONGNVARCHAR, LONGVARCHAR, and NCLOB. Column sizes for long binary types may be managed with the limits ODataBinaryColumnSizeLimit and ODataIncludeBinaryLongData. Column sizes for long character types may be managed with the limits ODataCharacterColumnSizeLimit and ODataIncludeCharacterLongData. Refer to the following documentation resources for details: Entity Data Model (EDM) types for OData Version 4, Manage Limits view, and Limits API.
The Hybrid Data Pipeline server and On-Premises Connector have been upgraded to install and use Tomcat 9.0.95. (On-Premises Connector version 4.6.2.1046)
For Linux, the ICU library files that are installed with the driver have been upgraded to version 74.1. In addition, the ICU library file names have changed. For the 32-bit driver, the ICU file name has changed from libivicu28.so to libivicu.so. For the 64-bit driver, the ICU file name has changed from libddicu28.so to libddicu.so. (ODBC driver version 4.6.2.340, November 21, 2024)
For Windows, the ICU library files that are installed with the driver have been upgraded to version 74.1. As a part of this upgrade, the ICU library file names have changed. For the 32-bit driver, the ICU file name has changed from ivicu28.dll to ivicu.dll. For the 64-bit driver, the ICU file name has changed from ddicu28.dll to ddicu.dll. (ODBC driver version 4.6.2.340, November 21, 2024)
Google has ended support for Universal Analytics (also referred to as Google Analytics 3). Therefore, Google Analytics 3 support has been removed from Hybrid Data Pipeline. Google Analytics 4 support was added to Hybrid Data Pipeline with the 4.6.1.1854 release of the server. Google Analytics 4 continues to be supported and maintained as a Hybrid Data Pipeline data store. Refer to Google Analytics 4 parameters for details. (On-Premises Connector version 4.6.2.1046)
The driver is now compiled with an upgraded compiler for Windows platforms. As a result, you must have Microsoft Visual C/C++ runtime version 14.40.33810 or higher on your machine to run the driver. (ODBC driver version 4.6.2.340, November 21, 2024)
When executing a SQL query that ends with a semicolon against an Oracle data source, the error "ORA-03137: malformed TTC packet from client rejected" was returned. (JDBC driver version 4.6.2.403)
When using a JDBC third-party connector, the OData schema map could not be refreshed using the Web UI.
Resource leaks occurred with SSL connections to OpenEdge, MySQL, Sybase, Oracle Service Cloud, and Db2 data sources. These leaks resulted in a "Too many open files" exception and caused the server to fail.
On the data source page for the SAP S/4HANA data store, the Connector ID parameter for the On-Premises Connector was missing.
On the advanced tab of the SAP S4/HANA data store page, the "Extended Options" parameter was not exposed.
See Hybrid Data Pipeline known issues for details.