Possible JDBC IMPORT failure for CLOB columns
Details
| Detail name | Value |
|---|---|
| Changelog Number | 4640 |
| Type | Bug |
| Status | Resolved |
| Affected Versions | EXASOL 6.0.0 |
| Fix Versions | EXASOL 6.0.2 |
| Resolution Date | 2017-06-06 |
If IMPORTing data from a JDBC source into a previously nonexistent table, the IMPORT may fail if the JDBC driver represents the column as a CLOB column. This is because a JDBC CLOB column's metadata are not correctly fetched during the IMPORT, and if a destination table does not already exist in Exasol, this incorrect metadata is used for the table, which can lead to a failure.
*Example:
SELECT * FROM ( IMPORT FROM JDBC AT <JDBC_CONN> STATEMENT 'SELECT <CLOB_COLUMN> FROM <TABLE>' );
Possible workarounds:
- Create a destination table in Exasol and IMPORT into it.
- Cast the affected column to another type, which is not represented as CLOB (e.g., VARCHAR).
- Use a different driver.
