topic Re: TERADATA UTF-8 PROBLEM in SAS Enterprise Guide

TERADATA UTF-8 PROBLEM

AliZiya — Fri, 15 Mar 2024 12:18:58 GMT

Hello,

We are using sas eg 9.4 on our clients. We are using here TERADATA to connect the database. And we have libname options here. Our clients changed the encoding of TERADATA to utf-8. Then our words on tables are corrupted. The letters for example: i,ö,ş seems like corrupted.

We had changed the sas.v9.cfg encoding as UTF-8. Also, the clispb.dat file which we are using connect the database added new properties as charset=utf8.

But after this changes, Nothing has changed on our tables. Can you help us?

Thanks

Re: TERADATA UTF-8 PROBLEM

onuroruc — Fri, 15 Mar 2024 12:24:00 GMT

I have same problem. Please help

Re: TERADATA UTF-8 PROBLEM

abdullahdogan — Fri, 15 Mar 2024 12:26:10 GMT

I have same problem too

Re: TERADATA UTF-8 PROBLEM

AhmedAl_Attar — Fri, 15 Mar 2024 12:33:12 GMT

Hi,

Have a look at the following resources, they may help you

- Multilingual Computing_with SAS 9.4

- SAS0296-2017.pdf

- The SAS® Encoding Journey: A Byte at a Time

- Demystifying and resolving common transcoding problems - SAS Users

- The Impact of Change from wlatin1 to UTF-8 Encoding in SAS Environment (pharmasug.org)

- 64089 - Frequently asked questions about preparing your site to use UTF-8 SAS® session encoding

- 15597 - How to convert SAS® data set encoding

Hope this helps,

Ahmed

Re: TERADATA UTF-8 PROBLEM

AliZiya — Fri, 15 Mar 2024 12:48:48 GMT

Ahmed, Thanks but this links didn't change anything 😞

Re: TERADATA UTF-8 PROBLEM

AhmedAl_Attar — Fri, 15 Mar 2024 13:08:04 GMT

@AliZiya

I'm not sure what you got out of the links I sent!?

Did you get a chance to even read them?

"(R)DBMS Tables
........ The trick, then, is to make sure that the server knows the client’s encoding. In any case, as long as the SAS session encoding is equivalent to the RDBMS client encoding value, there is no data loss.
Each RDBMS client software application has its own way of being configured with the client application encoding. Client variables ensure that the transcoding from the database encoding to the client’s encoding works correctly. See the following table for illustration.

RDBMS: Teradata

RDBMS client variable(s): charset_id, charset_type

Example: charset_id=UTF8, charset_type=N

1. You'll need to set the NLS_LANG on Linux, by asking your SAS Administrator to do the following

Add the following two lines to the <SASHome>/SASFoundation/9.4/bin/sasenv_local file on your SAS server

export charset_id=UTF8

export charset_type=N

2. Use SAS with UTF-8 encoding

<SASHome>/SASFoundation/9.4/bin/sas_u8

The above will ensure your utf-8 data extraction from Teradata comes over to SAS without data lose or disruption.

Re: TERADATA UTF-8 PROBLEM

AliZiya — Fri, 15 Mar 2024 13:39:19 GMT

Hi Ahmed,
Thanks you for support! We are controlled the sasenv_local and problem is fixed. Beacause we have noticed that we didn't change the new path of teradata client. We changed it and its resolved.
Thanks for giving inspiring us!!