EXPORT INTO ORA: Export of CHAR columns into Oracle may unexpectedly fail

Detail name	Value
Changelog Number	21193
Type	Bug
Status	Resolved
Affected Versions	Exasol 7.1.0, Exasol 8.0.0
Fix Versions	Exasol 8.34.0, Exasol 8.29.9
Resolution Date	2025-04-02

Description

An EXPORT of a CHAR column from Exasol to Oracle using a native connection (i.e. ORA) may unexpectedly fail. This is due to incorrect character encodings.

Examples

Oracle table

create table test_mb (a char(1 char));

Exasol tables

create table test_sb (a char(1) ascii);
insert into test_sb values '0', '1';

create table test_mb (a char(1) utf8);
insert into test_mb values 'ä', 'ö';

Exasol statements that incorrectly fail

export test_sb into ora at ... table test_mb;
--ETL-4300: Oracle tool failed with error code '24381' and message 'ORA-24381: error(s) in array DML

export test_mb into ora at ... table test_mb;
--ETL-4300: Oracle tool failed with error code '24381' and message 'ORA-24381: error(s) in array DML

Workaround

Affected EXPORT statements can be executed using a JDBC connection instead of a native ORA connection.

export test_sb into jdbc at ... table test_mb;

Fix

The issue has been fixed such that the EXPORT statements will succeed as expected.