Issues fixed in DataDirect JDBC 6.0

When attempting to connect, the driver returned a general error if the {{DATE_OUTPUT_FORMAT}} session parameter was set to {{DD-MON-YYYY}}.

The driver defaulted to using nvarchar(4000) for parameters in prepared statements, which caused high CPU utilization on the server due to implicit data type conversions.

The driver incorrectly cleared pagination parameters during endpoint sampling when the mandatory MaximumPageSize property was missing. This issue has been resolved, and the driver now provides a clear error message when required paging properties are not specified.

When attempting to connect to Oracle using SSL, the driver returned an error when the connection string exceeded a specific character threshold due to a long service name.

When attempting to retrieve schema information, the driver failed to return results for catalogs with names containing hyphens.

When attempting to retrieve large datasets from SAP S/4HANA, the driver failed to fetch the complete result set when the server enforced server-driven paging.

Add the Snowflake driver license to Oracle GoldenGate branded drivers

The driver failed to connect to Snowflake when specifying a lowercase or case-sensitive role name with URL-encoded double quotes.

When invoking the isValid() API to validate the connection, the driver executedan incorrect query. As a result, errors were logged in the database logs.

The driver logged verbose informational and warning messages from the Apache Arrow library to the console by default.

AutoRest JDBC driver failed to honor the ValidateServerCertificate option=false option while connecting the endpoint through the proxy server

The JDBC drivers returned a generic SQLException instead of the SQLNonTransientException when accessing closed resources.

The JDBC drivers returned a generic SQLException instead of the SQLNonTransientException when accessing closed resources.

The driver returned a generic SQLException instead of a SQLNonTransientException when accessing closed resources.

The drivers returned the generic SQLException instead of the SQLNonTransientException when accessing closed resources.

The JDBC drivers threw a generic SQLException exception instead of the SQLNonTransientException when accessing closed resources.

The DD JDBC drivers threw the generic ‘SQLException’ instead of ‘SQLNonTransientException’ when accessing closed resources.

The driver returned a generic SQLException instead of SQLNonTransientException when accessing closed resources.

The DataDirect JDBC drivers threw the generic ‘SQLException’ instead of ‘SQLNonTransientException’ when accessing closed resources.

The driver returned a generic SQLException instead of the SQLNonTransientException when accessing closed resources.

The object closed scenario returned a generic SQLException instead of a dedicated SQLNonTransientException.

The DD JDBC drivers threw the generic ‘SQLException’ instead of ‘SQLNonTransientException’ when accessing closed resources.

The driver returned a generic {{SQLException}} instead of the more specific {{SQLNonTransientException}} when an application attempted to access a closed resource.

The DD JDBC drivers threw the generic ‘SQLException’ instead of ‘SQLNonTransientException’ when accessing closed resources.

Glasswall scanner reported multiple .so dependencies in the driver as malware.

Vulnerabilities found in Snowflake, Greenplum, and Google BigQuery JDBC Driver JAR files by Glasswall scanner

In a FIPS-compliant environment, the customer attempted to connect to Snowflake using the JDBC driver with key-pair authentication but encountered an error, while the native Snowflake driver functioned without any issues.

The driver failed to recognize a stored procedure when null values are passed to the UUID parameters.

When an application sent parameters in the body of a POST request for Select statements, the driver returned the first page but did not send any subsequent pages.

The driver returned a generic SQLException instead of a SQLNonTransientException when accessing closed resources.

The driver returned a “Hexadecimal string is invalid” error while fetching the Varchar data type with getBytes() method.

The driver failed to execute SELECT queries containing comments at the end and returned a 'syntax error at end of input' message.

Upgraded the driver’s BouncyCastle library to version 1.83.

When attempting to run a stored procedure, the driver threw a null pointer exception.

Connection to AstraDB using token‑based authentication failed with a null‑pointer exception when supplying Secure Connection Bundle details.

Glasswall scanner detected vulnerabilities detected in driver Jar files.

When executing boolean ret = stmt.execute();, the driver incorrectly returned false instead of the expected true.

The driver ignored the filterable=false metadata and pushed filters for non‑filterable Boolean fields to the server.

The driver returned a null CatalogName for system schemas when invoking getSchemas(connection.getCatalog(), null).

When connected to Azure Synapse, the driver returned an unsupported error message during query execution, preventing proper identification of the issue.

The connector mishandled a PATCH request to insert a child table into a third-party API.

When attempting to insert array data, the driver returned a ClassCastException error.

When running the driver in a FIPS compliant environment, the driver OCSP validation flag prevented the driver from connection.

Calling {{DatabaseMetaData.getProcedureColumns}} on a standalone stored procedure returned combined metadata from both the standalone and packaged procedures when they share the same name, instead of returning only the standalone procedure’s columns.

The driver reported differing column type names for timestamp columns based on whether the metadata originated from DatabaseMetaData or ResultSetMetaData.

When executing a getSchemas() call, the driver did not return schemas whose names were enclosed in double quotes.

When filtering endpoints that require parameters using {{INFORMATION_SCHEMA.SYSTEM_COLUMNS_REQUIRED_FILTERS}}, the required filter was not exposed in the path for the {{PROPERTIESLIST}} endpoint.

The Cassandra JDBC driver did not support the ClusterNodes connection option for specifying multiple cluster node hostnames, unlike the ODBC Cassandra driver where this option was present.

The Composer was unable to retrieve data in tabular format for an endpoint.

When executing a CREATE TABLE statement that included double-quoted, lowercase standard column names, the driver returned a NullPointerException.

The driver returned an {{ORA-00910}} error when the query {{SELECT CAST('test' AS VARCHAR2(32767)) FROM dual}}  was executed in environments where Extended Data Types (EDT) were not enabled.

When attempting to insert Null values in a Boolean column, the driver returned the “Unhandled SQL type” error.

When attempting to connect to an LDAP server, the driver returned the "Not an instance of DirContext" error.

When invoking DatabaseMetadata.getTables, the connector did not return all the tables in the ResultSet.

When attempting to execute getFunctionColumns(), the driver did not return COLUMN_NAME for the unnamed function return types.

The JDBC API call {{setMaxRows()}} did not work correctly with the driver as compared to the expected functionality of the {{LIMIT}} clause.

The driver successfully connected to the dedicated pool in Azure Synapse Analytics. However, it encountered a StackOverflowError when attempting to connect to the serverless pool.

When using the driver, TIMESTAMP(N) columns (precision 1–12) reported a fixed scale of 6 instead of reflecting the precision defined at creation.

When attempting to execute getFunctionColumns(), the driver did not return COLUMN_NAME for the unnamed function return types.

When connecting to a partially contained database, the driver failed to retrieve metadata for stored procedures using the getProcedures catalog function.

When attempting to connect to an SSL-enabled, cloud-hosted instance, the driver returned the following error: "SCRAM channel binding check failed."

When executing a SELECT query that included the DISTINCT keyword, the driver returned incorrect results.

When attempting to fetch the object identifier for the Geometry data type, the driver returned "UNKNOWN".

When fetching metadata for BIT[50], CHARACTER[50], and CHAR[50] array types, the driver returned incorrect column sizes.

The driver does not expose the QualifyNormalizedNames property. This property allows you to prefix child tables (normalized from arrays and objects) with the names of parent objects.

Connections from Linux using a UNC path to the REST file fail with the exception “An unexpected error has occurred while loading the native schema map file.”

When attempting to execute a batch operation with AutoCommit set to false, the driver encountered a BatchUpdateException and returned an incorrect value for getLargeUpdateCounts().

When attempting to execute a batch operation with AutoCommit set to false, the driver encountered a BatchUpdateException and returned an incorrect value from getLargeUpdateCounts().

When attempting to connect to the server in FIPS mode, the driver returned the following error: "MD5 MessageDigest not available".

The driver failed during statement compilation when executing a parameterized insert into a {{BINARY}} column.

When attempting to read a VARCHAR2 column from a table in an Oracle 19c database configured with ZHT16BIG5 as the default character set, the driver returned the following error: “Transliteration failed. Reason: Destination buffer too small or partial character encountered. ErrorCode=0, SQLState=HY000.”

Catalog methods failed to return records when backslashes in table names were escaped in the catalog metadata calls.

Metadata APIs returned incorrect {{COLUMN_SIZE}} values for Db2z servers for the data types {{BIGINT}}, {{REAL}}, and {{DECFLOAT}}.

Metadata APIs returned incorrect {{COLUMN_SIZE}} values for Db2i servers for the data types GRAPHIC, VARGRAPHIC, NVARCHAR, DOUBLE, and REAL.

When attempting to run getSchemas(), the driver did not return the result set for the schema containing a backslash symbol in its name.

When attempting to run getSchemas(), the driver did not return the result set for the schema containing a single quotation mark in its name.

When calling getSchemas(), the driver did not return rows for the schemas containing underscores in their names.

Catalog methods failed to return records when the table name contained single quotes.

The getIndexInfo() API returned defined constraints along with indexes.

When sampling or querying data in lines of XML that contained attributes and plain text, the driver processed the attribute information but ignored the plain text data.

When attempting to connect to the server using NTLM authentication, the driver returned the following error: “java.lang.NoSuchMethodError”

When attempting to execute the getCatalogs() method, the driver returned results only for the database to which it was connected rather than for all databases.

When using the driver with Kerberos authentication, an initialization process resulted in a StackOverflowError.

For the data types FLOAT, REAL and NUMBER, the driver was not returning metadata that allowed a customer application to specifically identify the way such columns were created.

When calling the connection.getMetaData().getColumns() method, the driver returned a CHAR_OCTET_LENGTH value of 0 for a non-zero-length Char column.

The driver has been updated to remove all values that should be secured from generated log files.

The driver has been updated to remove all values that should be secured from generated log files.

When attempting to insert multiple invalid records using executeBatch(), the driver hung.

When attempting to insert multiple invalid records using executeBatch(), the driver hung.

When attempting to insert multiple invalid records using executeBatch(), the driver hung.

When attempting to insert multiple invalid records using executeBatch(), the driver hung.

An InvalidProtocolBufferException error was thrown when using the driver with version 1.9.0 of Kotlin.

The ODBC GoogleBigQuery driver does not honor the “UseStreamingInsert” connection option after Re-running the same job, causing a huge performance issue.

The driver has been updated to remove all values that should be secured from the string returned by calling getURL().

When attempting to fetch large number of rows, the driver returned the following error: “java.lang.ArrayIndexOutOfBoundsException".

When ServerMode=1 (Server), the driver hung when attempting to connect using SQLDriverConnectW.

When calling executeBatch() for stored procedures, the driver returned a NullPointerException.

When attempting to insert data into a column of a different data type using preparedStatement.executeBatch(), the driver returned the following error: “Value cannot be converted to the requested type.” Subsequently, when attempting to execute preparedStatement.close(), the driver hung.

When calling getProcedureColumn(), the driver returned an unexpected metadata value at position 0.

The driver returned the incorrect length for columns of the XML datatype.

The branding rules for the JSONObject class were incomplete.

The branding rules for the JSONObject class were incomplete.

The branding rules for the JSONObject class were incomplete.

The branding rules for the JSONObject class were incomplete.

The branding rules for the JSONObject class were incomplete.

The branding rules for the JSONObject class were incomplete.

The branding rules for the JSONObject class were incomplete.

The branding rules for the JSONObject class were incomplete.

The branding rules for the JSONObject class were incomplete.

The branding rules for the JSONObject class were incomplete.

The branding rules for the JSONObject class were incomplete.

The branding rules for the JSONObject class were incomplete.

The branding rules for the JSONObject class were incomplete.

The branding rules for the JSONObject class were incomplete.

When a DELETE statement included both a table alias and a WHERE clause, the driver sent a request to the server that could degrade query performance.

When attempting to create a stored procedure with multiple SQL queries, the driver returned the following error: “Unterminated dollar-quoted string”.

For TLS/SSL encryption, even when the ValidateServerCertificate option was set to false, the driver attempted to validate the certificates instead of ignoring them.

For TLS/SSL encryption, even when the ValidateServerCertificate option was set to false, the driver attempted to validate the certificates instead of ignoring them.

For TLS/SSL encryption, even when the ValidateServerCertificate option was set to false, the driver attempted to validate the certificates instead of ignoring them.

When ValidateServerCertificate=false, the driver attempted to validate the TrustStore path, instead of ignoring  truststore information.

For TLS/SSL encryption, even when the ValidateServerCertificate option was set to false, the driver attempted to validate the certificates instead of ignoring them.

The driver returned an error when attempting to execute the COPY command.

For TLS/SSL encryption, even when the ValidateServerCertificate option was set to false, the driver attempted to validate the certificates instead of ignoring them.

When ValidateServerCertificate=false, the driver attempted to validate the TrustStore path, instead of ignoring  truststore information.

A ServiceConfigurationError was thrown when the application used a different version of Jackson libraries than the driver.

The Oracle Kerberos connection failed when the AllowWeakCrypto configuration setting was disabled.

The driver was unable to use the Google BigQuery Streaming API when executing INSERT statements containing table, dataset, or project names that included a backtick (`) character.

Cannot connect to SSL data sources when RedHat system and JVM is configured in FIPS mode

When attempting to run a SELECT * query, the driver returned the following error: “414 (URI Too Long for GET)”.

The driver returned an incorrect timestamp value when attempting to increase the month value using TIMESTAMPADD.

The driver returned a license error when attempting to connect after installation with an OEM license key.

When attempting to install the branded driver, the installation failed.