<?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: The value applied to a Teradata integer was out of range - greater than 2147483647 in SAS Enterprise Guide</title>
    <link>https://communities.sas.com/t5/SAS-Enterprise-Guide/The-value-applied-to-a-Teradata-integer-was-out-of-range-greater/m-p/578736#M34381</link>
    <description>Hi Tom, yes, that's correct. I used the code you supplied to find the line that are not within that limit (defined as integer 4 byte in Teradata), appeared to happen to only 2 records (caused by entry data errors). Once I fixed the underlying data, I was able to upload everything without any issue. Thanks</description>
    <pubDate>Fri, 02 Aug 2019 15:01:03 GMT</pubDate>
    <dc:creator>MelissaN</dc:creator>
    <dc:date>2019-08-02T15:01:03Z</dc:date>
    <item>
      <title>The value applied to a Teradata integer was out of range - greater than 2147483647</title>
      <link>https://communities.sas.com/t5/SAS-Enterprise-Guide/The-value-applied-to-a-Teradata-integer-was-out-of-range-greater/m-p/578384#M34365</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;I ran a query in SAS to pull the data (63 columns, 18k rows) and then update this table to Teradata using ansi mode.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Create table APPS_TEMP as (select col1,col2,col3....col63 from abc)&lt;/P&gt;&lt;P&gt;&lt;FONT color="#0000ff" face="Courier New" size="3"&gt;libname&lt;/FONT&gt;&lt;FONT face="Courier New" size="3"&gt; Space &lt;/FONT&gt;&lt;FONT color="#0000ff" face="Courier New" size="3"&gt;teradata&lt;/FONT&gt; &lt;FONT color="#0000ff" face="Courier New" size="3"&gt;server&lt;/FONT&gt;&lt;FONT face="Courier New" size="3"&gt;=&lt;FONT color="#800080"&gt;'' &lt;/FONT&gt;&lt;/FONT&gt;&lt;FONT color="#0000ff" face="Courier New" size="3"&gt;user&lt;/FONT&gt;&lt;FONT face="Courier New" size="3"&gt;=&amp;amp;user_name &lt;/FONT&gt;&lt;FONT color="#0000ff" face="Courier New" size="3"&gt;password&lt;/FONT&gt;&lt;FONT face="Courier New" size="3"&gt;=&amp;amp;pwd &lt;/FONT&gt;&lt;FONT color="#0000ff" face="Courier New" size="3"&gt;schema&lt;/FONT&gt;&lt;FONT face="Courier New" size="3"&gt;=&lt;/FONT&gt;&lt;FONT color="#800080" face="Courier New" size="3"&gt;'Space'&lt;/FONT&gt; &lt;FONT color="#0000ff" face="Courier New" size="3"&gt;mode&lt;/FONT&gt;&lt;FONT face="Courier New" size="3"&gt;=ansi;&lt;/FONT&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;insert into Space.APPS&lt;/P&gt;&lt;P&gt;&amp;nbsp;select * from APPS_TEMP&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I was able to run this with no issue last month, but this month I got this error message&lt;/P&gt;&lt;P&gt;"ERROR: On an insert, update, or index operation, the value applied to a Teradata integer was out of range - greater than 2147483647."&lt;/P&gt;&lt;P&gt;Please advise how I could fix it.&lt;/P&gt;&lt;P&gt;Any help is greatly appreciated.&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;</description>
      <pubDate>Thu, 01 Aug 2019 13:09:06 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Enterprise-Guide/The-value-applied-to-a-Teradata-integer-was-out-of-range-greater/m-p/578384#M34365</guid>
      <dc:creator>MelissaN</dc:creator>
      <dc:date>2019-08-01T13:09:06Z</dc:date>
    </item>
    <item>
      <title>Re: The value applied to a Teradata integer was out of range - greater than 2147483647</title>
      <link>https://communities.sas.com/t5/SAS-Enterprise-Guide/The-value-applied-to-a-Teradata-integer-was-out-of-range-greater/m-p/578586#M34374</link>
      <description>&lt;P&gt;Teradata probably uses a 4 byte integer format, and that is the largest number that can be contained within that format. Whereas SAS uses an 8 byte floating point format for numbers, and can store numbers with up to 15 digits.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;If you need to store the number accurately in Teradata, you'll need to change the variable assignment in Teradata to either 8 byte integer (if that exists in Teradata), or eight byte floating point.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;This will be a job for your database administrator, so start by talking to them.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Tom&lt;/P&gt;</description>
      <pubDate>Thu, 01 Aug 2019 22:34:55 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Enterprise-Guide/The-value-applied-to-a-Teradata-integer-was-out-of-range-greater/m-p/578586#M34374</guid>
      <dc:creator>TomKari</dc:creator>
      <dc:date>2019-08-01T22:34:55Z</dc:date>
    </item>
    <item>
      <title>Re: The value applied to a Teradata integer was out of range - greater than 2147483647</title>
      <link>https://communities.sas.com/t5/SAS-Enterprise-Guide/The-value-applied-to-a-Teradata-integer-was-out-of-range-greater/m-p/578589#M34375</link>
      <description>Hi Tom,&lt;BR /&gt;Thanks for your response. None of my integer values are more than 15 digits. The max length is only 7 digits. I tried to do format 9 for my integer values, but it is still not working.</description>
      <pubDate>Thu, 01 Aug 2019 22:45:45 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Enterprise-Guide/The-value-applied-to-a-Teradata-integer-was-out-of-range-greater/m-p/578589#M34375</guid>
      <dc:creator>MelissaN</dc:creator>
      <dc:date>2019-08-01T22:45:45Z</dc:date>
    </item>
    <item>
      <title>Re: The value applied to a Teradata integer was out of range - greater than 2147483647</title>
      <link>https://communities.sas.com/t5/SAS-Enterprise-Guide/The-value-applied-to-a-Teradata-integer-was-out-of-range-greater/m-p/578593#M34376</link>
      <description>&lt;P&gt;Don't worry about formats; they don't change the underlying value of the variable.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Let's check the easiest thing first; run this code on your data. If there's a value that's not within limits, the error diagnostic will show you the line and the variable.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Tom&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;PRE&gt;&lt;CODE class=" language-sas"&gt;data _null_;
set abc;
if col1 &amp;gt; 2100000000 | col1 &amp;lt; -2100000000 then abort;
if col2 &amp;gt; 2100000000 | col2 &amp;lt; -2100000000 then abort;
if col3 &amp;gt; 2100000000 | col3 &amp;lt; -2100000000 then abort;
if col4 &amp;gt; 2100000000 | col4 &amp;lt; -2100000000 then abort;
if col5 &amp;gt; 2100000000 | col5 &amp;lt; -2100000000 then abort;
if col6 &amp;gt; 2100000000 | col6 &amp;lt; -2100000000 then abort;
if col7 &amp;gt; 2100000000 | col7 &amp;lt; -2100000000 then abort;
if col8 &amp;gt; 2100000000 | col8 &amp;lt; -2100000000 then abort;
if col9 &amp;gt; 2100000000 | col9 &amp;lt; -2100000000 then abort;
if col10 &amp;gt; 2100000000 | col10 &amp;lt; -2100000000 then abort;
if col11 &amp;gt; 2100000000 | col11 &amp;lt; -2100000000 then abort;
if col12 &amp;gt; 2100000000 | col12 &amp;lt; -2100000000 then abort;
if col13 &amp;gt; 2100000000 | col13 &amp;lt; -2100000000 then abort;
if col14 &amp;gt; 2100000000 | col14 &amp;lt; -2100000000 then abort;
if col15 &amp;gt; 2100000000 | col15 &amp;lt; -2100000000 then abort;
if col16 &amp;gt; 2100000000 | col16 &amp;lt; -2100000000 then abort;
if col17 &amp;gt; 2100000000 | col17 &amp;lt; -2100000000 then abort;
if col18 &amp;gt; 2100000000 | col18 &amp;lt; -2100000000 then abort;
if col19 &amp;gt; 2100000000 | col19 &amp;lt; -2100000000 then abort;
if col20 &amp;gt; 2100000000 | col20 &amp;lt; -2100000000 then abort;
if col21 &amp;gt; 2100000000 | col21 &amp;lt; -2100000000 then abort;
if col22 &amp;gt; 2100000000 | col22 &amp;lt; -2100000000 then abort;
if col23 &amp;gt; 2100000000 | col23 &amp;lt; -2100000000 then abort;
if col24 &amp;gt; 2100000000 | col24 &amp;lt; -2100000000 then abort;
if col25 &amp;gt; 2100000000 | col25 &amp;lt; -2100000000 then abort;
if col26 &amp;gt; 2100000000 | col26 &amp;lt; -2100000000 then abort;
if col27 &amp;gt; 2100000000 | col27 &amp;lt; -2100000000 then abort;
if col28 &amp;gt; 2100000000 | col28 &amp;lt; -2100000000 then abort;
if col29 &amp;gt; 2100000000 | col29 &amp;lt; -2100000000 then abort;
if col30 &amp;gt; 2100000000 | col30 &amp;lt; -2100000000 then abort;
if col31 &amp;gt; 2100000000 | col31 &amp;lt; -2100000000 then abort;
if col32 &amp;gt; 2100000000 | col32 &amp;lt; -2100000000 then abort;
if col33 &amp;gt; 2100000000 | col33 &amp;lt; -2100000000 then abort;
if col34 &amp;gt; 2100000000 | col34 &amp;lt; -2100000000 then abort;
if col35 &amp;gt; 2100000000 | col35 &amp;lt; -2100000000 then abort;
if col36 &amp;gt; 2100000000 | col36 &amp;lt; -2100000000 then abort;
if col37 &amp;gt; 2100000000 | col37 &amp;lt; -2100000000 then abort;
if col38 &amp;gt; 2100000000 | col38 &amp;lt; -2100000000 then abort;
if col39 &amp;gt; 2100000000 | col39 &amp;lt; -2100000000 then abort;
if col40 &amp;gt; 2100000000 | col40 &amp;lt; -2100000000 then abort;
if col41 &amp;gt; 2100000000 | col41 &amp;lt; -2100000000 then abort;
if col42 &amp;gt; 2100000000 | col42 &amp;lt; -2100000000 then abort;
if col43 &amp;gt; 2100000000 | col43 &amp;lt; -2100000000 then abort;
if col44 &amp;gt; 2100000000 | col44 &amp;lt; -2100000000 then abort;
if col45 &amp;gt; 2100000000 | col45 &amp;lt; -2100000000 then abort;
if col46 &amp;gt; 2100000000 | col46 &amp;lt; -2100000000 then abort;
if col47 &amp;gt; 2100000000 | col47 &amp;lt; -2100000000 then abort;
if col48 &amp;gt; 2100000000 | col48 &amp;lt; -2100000000 then abort;
if col49 &amp;gt; 2100000000 | col49 &amp;lt; -2100000000 then abort;
if col50 &amp;gt; 2100000000 | col50 &amp;lt; -2100000000 then abort;
if col51 &amp;gt; 2100000000 | col51 &amp;lt; -2100000000 then abort;
if col52 &amp;gt; 2100000000 | col52 &amp;lt; -2100000000 then abort;
if col53 &amp;gt; 2100000000 | col53 &amp;lt; -2100000000 then abort;
if col54 &amp;gt; 2100000000 | col54 &amp;lt; -2100000000 then abort;
if col55 &amp;gt; 2100000000 | col55 &amp;lt; -2100000000 then abort;
if col56 &amp;gt; 2100000000 | col56 &amp;lt; -2100000000 then abort;
if col57 &amp;gt; 2100000000 | col57 &amp;lt; -2100000000 then abort;
if col58 &amp;gt; 2100000000 | col58 &amp;lt; -2100000000 then abort;
if col59 &amp;gt; 2100000000 | col59 &amp;lt; -2100000000 then abort;
if col60 &amp;gt; 2100000000 | col60 &amp;lt; -2100000000 then abort;
if col61 &amp;gt; 2100000000 | col61 &amp;lt; -2100000000 then abort;
if col62 &amp;gt; 2100000000 | col62 &amp;lt; -2100000000 then abort;
if col63 &amp;gt; 2100000000 | col63 &amp;lt; -2100000000 then abort;
run;&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Thu, 01 Aug 2019 23:36:20 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Enterprise-Guide/The-value-applied-to-a-Teradata-integer-was-out-of-range-greater/m-p/578593#M34376</guid>
      <dc:creator>TomKari</dc:creator>
      <dc:date>2019-08-01T23:36:20Z</dc:date>
    </item>
    <item>
      <title>Re: The value applied to a Teradata integer was out of range - greater than 2147483647</title>
      <link>https://communities.sas.com/t5/SAS-Enterprise-Guide/The-value-applied-to-a-Teradata-integer-was-out-of-range-greater/m-p/578596#M34377</link>
      <description>Thanks Tom, I can try that to see if the culprit shows up. Just to clarify that I only need to check the integer columns correct? Thanks.</description>
      <pubDate>Fri, 02 Aug 2019 00:27:04 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Enterprise-Guide/The-value-applied-to-a-Teradata-integer-was-out-of-range-greater/m-p/578596#M34377</guid>
      <dc:creator>MelissaN</dc:creator>
      <dc:date>2019-08-02T00:27:04Z</dc:date>
    </item>
    <item>
      <title>Re: The value applied to a Teradata integer was out of range - greater than 2147483647</title>
      <link>https://communities.sas.com/t5/SAS-Enterprise-Guide/The-value-applied-to-a-Teradata-integer-was-out-of-range-greater/m-p/578722#M34380</link>
      <description>&lt;P&gt;I'm glad this helped you. Just to confirm, yes, the code I supplied would only be used on the variables that are defined as 4 byte integer in Teradata. Any variables that are 8 byte integer or any length of floating point would not have a problem (although with floating point, you need to understand at what point you'll start to lose low-end digits with integers).&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Tom&lt;/P&gt;</description>
      <pubDate>Fri, 02 Aug 2019 14:42:43 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Enterprise-Guide/The-value-applied-to-a-Teradata-integer-was-out-of-range-greater/m-p/578722#M34380</guid>
      <dc:creator>TomKari</dc:creator>
      <dc:date>2019-08-02T14:42:43Z</dc:date>
    </item>
    <item>
      <title>Re: The value applied to a Teradata integer was out of range - greater than 2147483647</title>
      <link>https://communities.sas.com/t5/SAS-Enterprise-Guide/The-value-applied-to-a-Teradata-integer-was-out-of-range-greater/m-p/578736#M34381</link>
      <description>Hi Tom, yes, that's correct. I used the code you supplied to find the line that are not within that limit (defined as integer 4 byte in Teradata), appeared to happen to only 2 records (caused by entry data errors). Once I fixed the underlying data, I was able to upload everything without any issue. Thanks</description>
      <pubDate>Fri, 02 Aug 2019 15:01:03 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Enterprise-Guide/The-value-applied-to-a-Teradata-integer-was-out-of-range-greater/m-p/578736#M34381</guid>
      <dc:creator>MelissaN</dc:creator>
      <dc:date>2019-08-02T15:01:03Z</dc:date>
    </item>
  </channel>
</rss>

