<?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 Transcoding errors in Netezza in Administration and Deployment</title>
    <link>https://communities.sas.com/t5/Administration-and-Deployment/Transcoding-errors-in-Netezza/m-p/383588#M9650</link>
    <description>&lt;P&gt;Morning team,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have a weird one this morning....&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Last night we implemented hotfix&amp;nbsp;Z29004 for SAS Access to Netezza 9.4_M3 on RHEL 6 to fix the error described in SAS Note &lt;A href="http://support.sas.com/kb/58/291.html" target="_blank"&gt;http://support.sas.com/kb/58/291.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;This worked 100% and the row limits are now being used correctly in E Guide. Ok.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Then we started having transcoding errors when reading data from Netezza similar to what is descibed in this SAS Note:&amp;nbsp;&amp;nbsp;&lt;A href="http://support.sas.com/kb/59/905.html" target="_blank"&gt;http://support.sas.com/kb/59/905.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Weird thing is, this very same hotfix should have FIXED the transcoding errors, now it seem to have INTRODUCED the issue.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Any ideas ?&lt;/P&gt;</description>
    <pubDate>Fri, 28 Jul 2017 08:47:22 GMT</pubDate>
    <dc:creator>nhvdwalt</dc:creator>
    <dc:date>2017-07-28T08:47:22Z</dc:date>
    <item>
      <title>Transcoding errors in Netezza</title>
      <link>https://communities.sas.com/t5/Administration-and-Deployment/Transcoding-errors-in-Netezza/m-p/383588#M9650</link>
      <description>&lt;P&gt;Morning team,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I have a weird one this morning....&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Last night we implemented hotfix&amp;nbsp;Z29004 for SAS Access to Netezza 9.4_M3 on RHEL 6 to fix the error described in SAS Note &lt;A href="http://support.sas.com/kb/58/291.html" target="_blank"&gt;http://support.sas.com/kb/58/291.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;This worked 100% and the row limits are now being used correctly in E Guide. Ok.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Then we started having transcoding errors when reading data from Netezza similar to what is descibed in this SAS Note:&amp;nbsp;&amp;nbsp;&lt;A href="http://support.sas.com/kb/59/905.html" target="_blank"&gt;http://support.sas.com/kb/59/905.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Weird thing is, this very same hotfix should have FIXED the transcoding errors, now it seem to have INTRODUCED the issue.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Any ideas ?&lt;/P&gt;</description>
      <pubDate>Fri, 28 Jul 2017 08:47:22 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Administration-and-Deployment/Transcoding-errors-in-Netezza/m-p/383588#M9650</guid>
      <dc:creator>nhvdwalt</dc:creator>
      <dc:date>2017-07-28T08:47:22Z</dc:date>
    </item>
    <item>
      <title>Re: Transcoding errors in Netezza</title>
      <link>https://communities.sas.com/t5/Administration-and-Deployment/Transcoding-errors-in-Netezza/m-p/384176#M9875</link>
      <description>Since your experiencing that this is connected to the hot fix, I think that SAS tech support is the way forward.</description>
      <pubDate>Mon, 31 Jul 2017 08:04:43 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Administration-and-Deployment/Transcoding-errors-in-Netezza/m-p/384176#M9875</guid>
      <dc:creator>LinusH</dc:creator>
      <dc:date>2017-07-31T08:04:43Z</dc:date>
    </item>
    <item>
      <title>Re: Transcoding errors in Netezza</title>
      <link>https://communities.sas.com/t5/Administration-and-Deployment/Transcoding-errors-in-Netezza/m-p/384180#M9876</link>
      <description>&lt;P&gt;Ah...thanks for reminding me....&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Turns out, the LANG= variable on our RHEL 6 was set to UTF-8 whereas SAS and Netezza was set to LATIN.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;But here is&amp;nbsp; the gotcha.....The RHEL 6 setting didn't change, so the question is how did it work before the hotfix&amp;nbsp;?? Turns out, with the Hotfix, SAS now enforces that the LANG= variable be correctly set, which is of course the right thing. Here is the real gotcha....This was not mentioned in the&amp;nbsp;hotfix documentation, so we simply applied the hotfix without any further changes. We have asked SAS Tech Support to update the hotfix documentation with this info. So if your RHEL 6 is running UTF-8 by default and you apply this hotfix, it will trigger this condition.&lt;/P&gt;</description>
      <pubDate>Mon, 31 Jul 2017 08:28:54 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Administration-and-Deployment/Transcoding-errors-in-Netezza/m-p/384180#M9876</guid>
      <dc:creator>nhvdwalt</dc:creator>
      <dc:date>2017-07-31T08:28:54Z</dc:date>
    </item>
  </channel>
</rss>

