<?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 SAS task name is [OBJECT_E]  Segmentation Violation in Administration and Deployment</title>
    <link>https://communities.sas.com/t5/Administration-and-Deployment/The-SAS-task-name-is-OBJECT-E-Segmentation-Violation/m-p/559863#M16291</link>
    <description>This is something to raise with SAS technical support.</description>
    <pubDate>Sat, 18 May 2019 11:19:45 GMT</pubDate>
    <dc:creator>SimonDawson</dc:creator>
    <dc:date>2019-05-18T11:19:45Z</dc:date>
    <item>
      <title>The SAS task name is [OBJECT_E]  Segmentation Violation</title>
      <link>https://communities.sas.com/t5/Administration-and-Deployment/The-SAS-task-name-is-OBJECT-E-Segmentation-Violation/m-p/559705#M16283</link>
      <description>&lt;P&gt;We are installing SAS/Access to Redshift and try to connect to Redshift database,the installation is complete , however we are getting the below error while trying to execute the statement . (Version of SAS - 9.4M5 , linux machine)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;LIBNAME A4 redshift PRESERVE_COL_NAMES=YES PRESERVE_TAB_NAMES=YES dsn=redaccess SCHEMA=aaaaa USER=xxxxx password=yyyyy;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;ERROR: An exception has been encountered.&lt;BR /&gt;Please contact technical support and provide them with the following traceback information:&lt;BR /&gt;&lt;BR /&gt;The SAS task name is [OBJECT_E]&lt;BR /&gt;Segmentation Violation&lt;BR /&gt;&lt;BR /&gt;Traceback of the Exception:&lt;BR /&gt;&lt;BR /&gt;/sascommon/SAS/SASHome/SASFoundation/9.4/sasexe/sas(+0x1666ce) [0x55f4bf5fc6ce]&lt;BR /&gt;/sascommon/SAS/SASHome/SASFoundation/9.4/sasexe/sas(+0x4e7df) [0x55f4bf4e47df]&lt;BR /&gt;/sascommon/SAS/SASHome/SASFoundation/9.4/sasexe/tkmk.so(bkt_signal_handler+0x144) [0x2b8a79526a44]&lt;BR /&gt;/usr/lib64/libpthread.so.0(+0xf5d0) [0x2b8a781c95d0]&lt;BR /&gt;/sascommon/SAS/SASHome/SASFoundation/9.4/sasexe/sasiorst(pgcon+0x594e) [0x2b8acb387e7e]&lt;BR /&gt;/sascommon/SAS/SASHome/SASFoundation/9.4/sasexe/sasxdbi(dbicon+0xa03) [0x2b8acb655cd3]&lt;BR /&gt;/sascommon/SAS/SASHome/SASFoundation/9.4/sasexe/sasxdbi(yhelasg+0x959) [0x2b8acb62dc19]&lt;BR /&gt;/sascommon/SAS/SASHome/SASFoundation/9.4/sasexe/sasyh(yyhlasn+0x203) [0x2b8a7fd59d53]&lt;BR /&gt;/sascommon/SAS/SASHome/SASFoundation/9.4/sasexe/sasyh(yhlasn2+0x594) [0x2b8a7fd52374]&lt;BR /&gt;/sascommon/SAS/SASHome/SASFoundation/9.4/sasexe/sasxshel(ytlibf+0x3d6) [0x2b8a89895ab6]&lt;BR /&gt;/sascommon/SAS/SASHome/SASFoundation/9.4/sasexe/sasxshel(yasany+0x198e) [0x2b8a898783ee]&lt;BR /&gt;/sascommon/SAS/SASHome/SASFoundation/9.4/sasexe/sasxshel(yasany2+0xcb) [0x2b8a8987690b]&lt;BR /&gt;/sascommon/SAS/SASHome/SASFoundation/9.4/sasexe/sasxshel(yttknx+0x1402) [0x2b8a89899332]&lt;BR /&gt;/sascommon/SAS/SASHome/SASFoundation/9.4/sasexe/sasxshel(yalexec+0x5e9) [0x2b8a898bbba9]&lt;BR /&gt;/sascommon/SAS/SASHome/SASFoundation/9.4/sasexe/sasxshel(yalinln+0x2f5) [0x2b8a898bf2d5]&lt;BR /&gt;/sascommon/SAS/SASHome/SASFoundation/9.4/sasexe/sasxshel(yalproc+0x18e) [0x2b8a898b944e]&lt;BR /&gt;/sascommon/SAS/SASHome/SASFoundation/9.4/sasexe/sasxobj(sasxobj+0x370) [0x2b8ab972d7d0]&lt;BR /&gt;/sascommon/SAS/SASHome/SASFoundation/9.4/sasexe/sas(vvtentr+0x18a) [0x55f4bf4e433a]&lt;BR /&gt;/usr/lib64/libpthread.so.0(+0x7dd5) [0x2b8a781c1dd5]&lt;BR /&gt;/usr/lib64/libc.so.6(clone+0x6d) [0x2b8a78c10ead]&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;SAS WTABORT (OBJECT_EXECUTIVE) The SAS System has detected an abort condition. An Exception occurred during wthtrm().&lt;BR /&gt;Please Contact Technical Support.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The required LD_LIBRARY_PATH is set and odbc.ini is set.&lt;/P&gt;&lt;P&gt;This works in the lower environment as expected.&lt;/P&gt;</description>
      <pubDate>Fri, 17 May 2019 16:58:04 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Administration-and-Deployment/The-SAS-task-name-is-OBJECT-E-Segmentation-Violation/m-p/559705#M16283</guid>
      <dc:creator>pururshothaman</dc:creator>
      <dc:date>2019-05-17T16:58:04Z</dc:date>
    </item>
    <item>
      <title>Re: The SAS task name is [OBJECT_E]  Segmentation Violation</title>
      <link>https://communities.sas.com/t5/Administration-and-Deployment/The-SAS-task-name-is-OBJECT-E-Segmentation-Violation/m-p/559863#M16291</link>
      <description>This is something to raise with SAS technical support.</description>
      <pubDate>Sat, 18 May 2019 11:19:45 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Administration-and-Deployment/The-SAS-task-name-is-OBJECT-E-Segmentation-Violation/m-p/559863#M16291</guid>
      <dc:creator>SimonDawson</dc:creator>
      <dc:date>2019-05-18T11:19:45Z</dc:date>
    </item>
    <item>
      <title>Re: The SAS task name is [OBJECT_E]  Segmentation Violation</title>
      <link>https://communities.sas.com/t5/Administration-and-Deployment/The-SAS-task-name-is-OBJECT-E-Segmentation-Violation/m-p/560404#M16315</link>
      <description>Thanks Simon , we already have a ticket open with technical support team,&lt;BR /&gt;&lt;BR /&gt;We will keep it updated to this topic .</description>
      <pubDate>Tue, 21 May 2019 08:58:23 GMT</pubDate>
      <guid>https://communities.sas.com/t5/Administration-and-Deployment/The-SAS-task-name-is-OBJECT-E-Segmentation-Violation/m-p/560404#M16315</guid>
      <dc:creator>pururshothaman</dc:creator>
      <dc:date>2019-05-21T08:58:23Z</dc:date>
    </item>
  </channel>
</rss>

