error due to unmatched encoding to another host, such as WINDOWS_64

WorkingMan — Fri, 01 May 2020 10:10:58 GMT

I hit error when I run a job in SAS DI Studio. The transformation it does is to modify the data inside this table. This table is DIM.ACCOUNT_DIM

If I run the libname statement for DIM, I can see the table and its data in SAS EG. However, when i try to run the job, it has error message:

ERROR: File DIM.ACCOUNT_DIM cannot be updated because its encoding does not match the session encoding or the file is in a format native to another host, such as WINDOWS_64.

In another thread here, there was a guide provided below:

https://blogs.sas.com/content/sasdummy/2010/05/24/finding-the-foreigners-in-your-sas-environment/

However, the guide didn't provide solution.

I would not prefer to create a new library or create a table with a different name because this table has many dependencies.

I've also done some checking. The encoding for DIM.ACCOUNT_DIM is wlatin1_Western (Windows) whereas my server encoding is UTF-8.

How can i fix this without dumping the original table?

Re: error due to unmatched encoding to another host, such as WINDOWS_64

Kurt_Bremser — Fri, 01 May 2020 11:00:13 GMT

Run

data dim.account_dim;
set dim.account_dim;
run;

once. SAS should NOTE the Cross Environment Data Access, but that's it; if the original dataset is stored with a compress option, add it to the DATA statement; likewise, recreate any indexes if the dataset had such.

topic Re: error due to unmatched encoding to another host, such as WINDOWS_64 in Administration and Deployment

error due to unmatched encoding to another host, such as WINDOWS_64

Re: error due to unmatched encoding to another host, such as WINDOWS_64