After some discussions with Oracle JDBC folks, we figured that the JDBC driver should not try to convert between TIMESTAMP_WITHOUT_TIMEZONE and OffsetDateTime. This means that users can’t bind these types to native queries currently, because there we don’t know what JDBC type to use for binding/extraction.

We can try to create a special JdbcType that tries to figure out details based on the PreparedStatement and ResultSet, but not sure yet how reliable that could work.