SuiteAnalytics Connect JDBC Driver 8.10.190.0 — TCP Keep-Alive and Packaging Fixes

What changed

Oracle released JDBC driver 8.10.190.0 (June 1, 2026) for SuiteAnalytics Connect. The driver is available for Windows, Linux, and macOS.

Fixes in this version:

• TCP keep-alive — Corrects keep-alive behavior in certain configurations. Previous versions (starting with 8.10.136.0) introduced the TCPKeepAlive connection-string parameter and OS-level KeepAliveTime support; this release addresses edge cases where that logic misfired.
• Error-message branding — Fixes the JDBC driver branding prefix in error messages, which could cause log-parsing or monitoring tools keyed on the old prefix to miss exceptions.
• JAR packaging — Resolves a packaging issue in the distributed JAR.

SHA-256 checksum of the JAR: 1234c5c7e259fc8df290ac969bbcbb6e8f249b5eb7ec01081c8720e0d73bfe10

Version history context

If you are upgrading from an older driver, be aware of the cumulative changes across versions:

• 8.10.184.0 (Dec 2025) — Security fixes (strongly recommended).
• 8.10.170.0 (Feb 2025) — Added java.sql.Connection.getSchema() support, required by the Boomi Database V2 connector. Requires NegotiateSSLClose=false.
• 8.10.147.0 (Aug 2023) — TLS 1.3 support (auto-enabled once Connect servers support it). Requires NegotiateSSLClose=false.
• 8.10.136.0 (Jul 2022) — Added TCPKeepAlive connection-string parameter and OS-level KeepAliveTime awareness. Requires NegotiateSSLClose=false.
• 8.10.85.0 (Sep 2019) — Minimum baseline version; fixes a 30-second logout delay. Requires NegotiateSSLClose=false.
• 7.20.50.0 (Jan 2016) — Introduced mandatory certificates, TLS 1.2 cipher suites, and required scompid/roleid parameters.

What to do

1. Download the latest driver from Oracle's Connect Driver Download Page and verify the SHA-256 checksum matches 1234c5c7...bfe10.
2. Verify your connection string includes NegotiateSSLClose=false. This has been required since 8.10.85.0.
3. If you rely on TCPKeepAlive=true in your connection string, test keep-alive behavior after upgrading — this release changes that logic.
4. If your monitoring or log-parsing tools match on the JDBC error-message prefix, update your regex/filters to account for the corrected branding string.
5. If you use the Boomi Database V2 connector, you already need ≥ 8.10.170.0; this upgrade is cumulative and compatible.
6. Minimum supported version remains 8.10.85.0. Anything on the 7.x line should be treated as end-of-life.

What Oracle did not specify

The release notes are vague on the exact TCP keep-alive edge cases fixed and do not clarify whether the error-message prefix change is cosmetic or affects programmatic exception handling. If you catch JDBC exceptions by message prefix in application code, test thoroughly after upgrading.