When syncing data from Oracle to Doris using SeaTunnel 2.3.9, users may face garbled characters if Oracle employs the ASCII character set. This issue arises because Doris anticipates data in proper UTF-8 encoding. The problem can be attributed to the way SeaTunnel reads data from Oracle's ResultSet. A strategy to resolve this is to intercept and re-encode the data as it is read, ensuring that characters are correctly encoded and displayed. Implementing charset parameters allows for this adjustment during data retrieval.
If Oracle is using a character set like ASCII, and you're syncing to Doris (which expects proper UTF-8 or other compatible encodings), Chinese characters can become unreadable.
The solution involves detecting the source encoding and re-encoding the data when it is retrieved from the ResultSet to prevent garbled characters.
Collection
[
|
...
]