<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic After changing encoding to utf 8 from latin1 , Issue with registering tables in SMC in Administration and Deployment</title>
    <link>https://communities.sas.com/t5/Administration-and-Deployment/After-changing-encoding-to-utf-8-from-latin1-Issue-with/m-p/569742#M16623</link>
    <description>&lt;P&gt;Hi All,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;After changing encoding to utf 8 from latin1 in sas , we are facing issue with registering tables in SMC. There are spaces showing up in table names. Below is the error when trying to register tables with spaces in table names.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;NOTE: The autoexec file, /sas/sasconfig/Lev1/SASApp1/WorkspaceServer/autoexec.sas, was executed at server initialization.&lt;BR /&gt;1 LIBNAME srcch1_1 ODBC READ_LOCK_TYPE=NOLOCK READBUFF=1000 DATAsrc=xxx SCHEMA=dbo USER=xxx&lt;BR /&gt;1 ! PASSWORD=XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX ;&lt;BR /&gt;NOTE: Libref SRCCH1_1 was successfully assigned as follows:&lt;BR /&gt;Engine: ODBC&lt;BR /&gt;Physical Name: xxx&lt;BR /&gt;2&lt;BR /&gt;2 The SAS System Friday, June 28, 2019 06:48:00 AM&lt;/P&gt;&lt;P&gt;NOTE: 34 table(s) not displayed/returned because the name is too long.&lt;BR /&gt;3 proc metalib;&lt;BR /&gt;4 omr (LIBURI="A5MSZA1O.BA0000SW" / project_reposid = "A5MSZA1O" );&lt;BR /&gt;5 REPORT(type = summary out = "tab_info");&lt;BR /&gt;6 SELECT ("A&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;End of log.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Fri, 28 Jun 2019 11:00:11 GMT</pubDate>
    <dc:creator>keerthi78890976</dc:creator>
    <dc:date>2019-06-28T11:00:11Z</dc:date>
    <item>
      <title>After changing encoding to utf 8 from latin1 , Issue with registering tables in SMC</title>
      <link>https://communities.sas.com/t5/Administration-and-Deployment/After-changing-encoding-to-utf-8-from-latin1-Issue-with/m-p/569742#M16623</link>
      <description>&lt;P&gt;Hi All,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;After changing encoding to utf 8 from latin1 in sas , we are facing issue with registering tables in SMC. There are spaces showing up in table names. Below is the error when trying to register tables with spaces in table names.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;NOTE: The autoexec file, /sas/sasconfig/Lev1/SASApp1/WorkspaceServer/autoexec.sas, was executed at server initialization.&lt;BR /&gt;1 LIBNAME srcch1_1 ODBC READ_LOCK_TYPE=NOLOCK READBUFF=1000 DATAsrc=xxx SCHEMA=dbo USER=xxx&lt;BR /&gt;1 ! PASSWORD=XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX ;&lt;BR /&gt;NOTE: Libref SRCCH1_1 was successfully assigned as follows:&lt;BR /&gt;Engine: ODBC&lt;BR /&gt;Physical Name: xxx&lt;BR /&gt;2&lt;BR /&gt;2 The SAS System Friday, June 28, 2019 06:48:00 AM&lt;/P&gt;&lt;P&gt;NOTE: 34 table(s) not displayed/returned because the name is too long.&lt;BR /&gt;3 proc metalib;&lt;BR /&gt;4 omr (LIBURI="A5MSZA1O.BA0000SW" / project_reposid = "A5MSZA1O" );&lt;BR /&gt;5 REPORT(type = summary out = "tab_info");&lt;BR /&gt;6 SELECT ("A&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;End of log.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 28 Jun 2019 11:00:11 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Administration-and-Deployment/After-changing-encoding-to-utf-8-from-latin1-Issue-with/m-p/569742#M16623</guid>
      <dc:creator>keerthi78890976</dc:creator>
      <dc:date>2019-06-28T11:00:11Z</dc:date>
    </item>
    <item>
      <title>Re: After changing encoding to utf 8 from latin1 , Issue with registering tables in SMC</title>
      <link>https://communities.sas.com/t5/Administration-and-Deployment/After-changing-encoding-to-utf-8-from-latin1-Issue-with/m-p/569883#M16626</link>
      <description>&lt;P&gt;This issue is fixed, added following option in sasenv_local file : export EASYSOFT_UNICODE=YES;&lt;/P&gt;</description>
      <pubDate>Fri, 28 Jun 2019 15:57:23 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Administration-and-Deployment/After-changing-encoding-to-utf-8-from-latin1-Issue-with/m-p/569883#M16626</guid>
      <dc:creator>keerthi78890976</dc:creator>
      <dc:date>2019-06-28T15:57:23Z</dc:date>
    </item>
  </channel>
</rss>

