<?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 Re: SAS Teradata Error in SAS Programming</title>
    <link>https://communities.sas.com/t5/SAS-Programming/SAS-Teradata-Error/m-p/508995#M136765</link>
    <description>&lt;P&gt;If you Google this error you will see it pops up on Teradata forums and definitely appears to be a&amp;nbsp;&lt;SPAN&gt;Teradata problem. I suggest you talk to your Teradata DBA to investigate.&lt;/SPAN&gt;&lt;/P&gt;</description>
    <pubDate>Wed, 31 Oct 2018 03:26:39 GMT</pubDate>
    <dc:creator>SASKiwi</dc:creator>
    <dc:date>2018-10-31T03:26:39Z</dc:date>
    <item>
      <title>SAS Teradata Error</title>
      <link>https://communities.sas.com/t5/SAS-Programming/SAS-Teradata-Error/m-p/508994#M136764</link>
      <description>I have a sas code which writes into a teradata table. I have been running this code for a year now and was working perfectly fine. I haven’t made any changes to the code but since last two days it is giving me the error below.&lt;BR /&gt;&lt;BR /&gt;ERROR: Teradata connection: CLI error 207 (no message text available) Correct error and restart as an APPEND process with option TPT_RESTART= YES. Since no checkpoints were taken, if the previous run used FIRSTOBS=n, uae the same value in the restart.&lt;BR /&gt;ERROR: ROLLBACK issued due to errors for data set mydata.dsn.data.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Code that inserts the data:&lt;BR /&gt;Proc sql;&lt;BR /&gt;Insert into mydata.dsn (multiload=yes tpt_restart=yes)&lt;BR /&gt;select a,&lt;BR /&gt;b,&lt;BR /&gt;c&lt;BR /&gt;from abc;&lt;BR /&gt;quit;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Is anyone familiar with this error message? The weird part is it was working fine and suddenly it is erroring out and nothing is updated in the code.&lt;BR /&gt;I am not sure if something changed in the Sas server or the database.&lt;BR /&gt;Any ideas or suggestions is highly apreciated. Thanks in advance.</description>
      <pubDate>Wed, 31 Oct 2018 02:47:36 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/SAS-Teradata-Error/m-p/508994#M136764</guid>
      <dc:creator>nickspencer</dc:creator>
      <dc:date>2018-10-31T02:47:36Z</dc:date>
    </item>
    <item>
      <title>Re: SAS Teradata Error</title>
      <link>https://communities.sas.com/t5/SAS-Programming/SAS-Teradata-Error/m-p/508995#M136765</link>
      <description>&lt;P&gt;If you Google this error you will see it pops up on Teradata forums and definitely appears to be a&amp;nbsp;&lt;SPAN&gt;Teradata problem. I suggest you talk to your Teradata DBA to investigate.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 31 Oct 2018 03:26:39 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/SAS-Teradata-Error/m-p/508995#M136765</guid>
      <dc:creator>SASKiwi</dc:creator>
      <dc:date>2018-10-31T03:26:39Z</dc:date>
    </item>
  </channel>
</rss>

