TIMESTAMP data in prepared statements and IMPORT/EXPORT may cause session termination

Detail name	Value
Changelog Number	22949
Type	Bug
Status	Resolved
Affected Versions	Exasol 8.32.0
Fix Versions	Exasol 2025.1.2, Exasol 2025.2.0
Resolution Date	2025-08-20

Problem

When reading TIMESTAMP or TIMESTAMP WITH LOCAL TIME ZONE column data from an older driver (see details below) while executing a prepared statement, the session could terminate leading to an error message such as the following.

ETL-4220: Closing prepared SQL statement failed. [Socket error. Connection interrupted. sslreadtimeout: connection closed by remote host

ETL-4220: Closing prepared SQL statement failed. [Database server not connected.]

Note: EXA IMPORT/EXPORT statements may also be affected if one Exasol instance has version 8.32+ and the other has a version before 8.32.

Affected driver versions

All drivers released before the nonaffected versions (see below) could trigger the issue.

Nonaffected driver versions

The following drivers will not trigger the issue.

• ODBC 24.2.0+
• SDK 24.2.0+
• JDBC 24.2.0+
• ADO.NET 24.2.0+
• All drivers using WebSocket API v5+

Workaround

JDBC IMPORT/EXPORT can be used as a workaround if the non-8.32+ Exasol instance uses a nonaffected JDBC driver (see above).

Fix

The issue is fixed such that older drivers (see above) can not cause this issue.