"ERROR: Unable to transcode data to/from UCS-2 encoding" when using DBCLIENT_MAX_BYTES=1 in Table Lo

[jozumhannes]

Hi everyone,

We are explicitly setting the DBCLIENT_MAX_BYTES=1 option in the LIBNAME statement when accessing Snowflake, since we manage the VARCHAR lengths manually on the Snowflake side and ensure they are large enough. This approach works fine in general.

However, when using the Table Loader transformation in SAS Data Integration Studio, we encounter the following error:

ERROR: Unable to transcode data to/from UCS-2 encoding.

The issue disappears when we set DBCLIENT_MAX_BYTES=2 instead.
Has anyone else experienced this behavior? Is this expected, or is there a recommended way to use DBCLIENT_MAX_BYTES=1 safely with Table Loader?

Thanks in advance!

[Tom]

What are you connecting to that is using UCS-2 encoding?

And no, you probably cannot force character strings to be only one byte long when each character is represented by two bytes.