BookmarkSubscribeRSS Feed
🔒 This topic is solved and locked. Need further help from the community? Please sign in and ask a new question.
keerthi78890976
Obsidian | Level 7

Hi All,

 

Registering tables was working fine with Latin1 encoding.After changing the sas encoding to utf-8 , we are facing issue while registering snowflake tables in SMC which is setup via snowflake odbc connector.There are spaces in the tables retrieved from snowflake database. Below is the error: 

 

NOTE: SAS Initialization used (Total process time):
real time 0.00 seconds
cpu time 0.00 seconds

NOTE: The autoexec file, /sas/sasconfig/Lev1/SASApp1/WorkspaceServer/autoexec.sas, was executed at server initialization.
1 LIBNAME testodbc ODBC PRESERVE_COL_NAMES=YES PRESERVE_TAB_NAMES=YES DATAsrc=xxx SCHEMA=xxx
1 ! USER=xxx  PASSWORD=XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX ;
NOTE: Libref TESTODBC was successfully assigned as follows:
Engine: ODBC
Physical Name: BOPS_DB_PROD
2
2 The SAS System Thursday, June 27, 2019 09:09:00 AM

NOTE: 25 table(s) not displayed/returned because the name is too long.
3 proc metalib;
4 omr (LIBURI="A5MSZA1O.BA0000TF" / project_reposid = "A5MSZA1O" );
5 REPORT(type = summary out = "tab_info");
6 SELECT ("C

========================================================================

If we are not mentioning PRESERVE_TAB_NAMES=YES, we are seeing the below error:

 

NOTE: The autoexec file, /sas/sasconfig/Lev1/SASApp1/WorkspaceServer/autoexec.sas, was executed at server initialization.
1 LIBNAME stg_dexp ODBC READBUFF=32767 INSERTBUFF=32767 AUTOCOMMIT=NO DBCOMMIT=10000 DATAsrc=xxx
1 ! SCHEMA=xxx USER=xx  PASSWORD=XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX ;
NOTE: Libref STG_DEXP was successfully assigned as follows:
Engine: ODBC
Physical Name: xxx
2
2 The SAS System Thursday, June 27, 2019 09:15:00 AM

NOTE: Due to the PRESERVE_TAB_NAMES=NO libname option setting, 7 table(s) have not been displayed/returned. 25 table(s) not
displayed/returned because the name is too long.

 

Could you please help on this issue.

1 ACCEPTED SOLUTION

Accepted Solutions
keerthi78890976
Obsidian | Level 7

This issue is fixed, added following option in sasenv_local file :

 

export EASYSOFT_UNICODE=YES;

View solution in original post

1 REPLY 1
keerthi78890976
Obsidian | Level 7

This issue is fixed, added following option in sasenv_local file :

 

export EASYSOFT_UNICODE=YES;

sas-innovate-wordmark-2025-midnight.png

Register Today!

Join us for SAS Innovate 2025, our biggest and most exciting global event of the year, in Orlando, FL, from May 6-9. Sign up by March 14 for just $795.


Register now!

Mastering the WHERE Clause in PROC SQL

SAS' Charu Shankar shares her PROC SQL expertise by showing you how to master the WHERE clause using real winter weather data.

Find more tutorials on the SAS Users YouTube channel.

Discussion stats
  • 1 reply
  • 1078 views
  • 0 likes
  • 1 in conversation