<?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: SCD type-2 integrity constraint warning in SAS Data Management</title>
    <link>https://communities.sas.com/t5/SAS-Data-Management/SCD-type-2-integrity-constraint-warning/m-p/461815#M14343</link>
    <description>&lt;P&gt;Doesn’t this mean the records you’re trying to insert, the 38 employee IDs, are already in the table?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;BLOCKQUOTE&gt;&lt;HR /&gt;&lt;a href="https://communities.sas.com/t5/user/viewprofilepage/user-id/8409"&gt;@Babloo&lt;/a&gt; wrote:&lt;BR /&gt;
&lt;P&gt;I've DI job which loads data to the physical table via SCD type-2 transformation. When I ran the job I received an error like&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;EM&gt;"WARNING: Add/Update failed for data set INS.EMPLOYEE because data value(s) do not comply with integrity constraint PRIM_KEY. (Occurred 38 times.) NOTE: There were 38 observations read from the data set WORK.ETLS_MATCH. &lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;NOTE: 0 observations added."&amp;nbsp;&lt;/EM&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Business key for my job is "Employee_ID" and there is no duplicates on &lt;SPAN&gt;Employee_ID&lt;/SPAN&gt;&amp;nbsp;and generated key is "Employee_RK". Could someone you help me understand the likely cause for this issue?&lt;/P&gt;
&lt;HR /&gt;&lt;/BLOCKQUOTE&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Sun, 13 May 2018 04:00:11 GMT</pubDate>
    <dc:creator>Reeza</dc:creator>
    <dc:date>2018-05-13T04:00:11Z</dc:date>
    <item>
      <title>SCD type-2 integrity constraint warning</title>
      <link>https://communities.sas.com/t5/SAS-Data-Management/SCD-type-2-integrity-constraint-warning/m-p/461814#M14342</link>
      <description>&lt;P&gt;I've DI job which loads data to the physical table via SCD type-2 transformation. When I ran the job I received an error like&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;EM&gt;"WARNING: Add/Update failed for data set INS.EMPLOYEE because data value(s) do not comply with integrity constraint PRIM_KEY. (Occurred 38 times.) NOTE: There were 38 observations read from the data set WORK.ETLS_MATCH. &lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;NOTE: 0 observations added."&amp;nbsp;&lt;/EM&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Business key for my job is "Employee_ID" and there is no duplicates on &lt;SPAN&gt;Employee_ID&lt;/SPAN&gt;&amp;nbsp;and generated key is "Employee_RK". Could someone you help me understand the likely cause for this issue?&lt;/P&gt;</description>
      <pubDate>Sun, 13 May 2018 03:35:40 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Data-Management/SCD-type-2-integrity-constraint-warning/m-p/461814#M14342</guid>
      <dc:creator>Babloo</dc:creator>
      <dc:date>2018-05-13T03:35:40Z</dc:date>
    </item>
    <item>
      <title>Re: SCD type-2 integrity constraint warning</title>
      <link>https://communities.sas.com/t5/SAS-Data-Management/SCD-type-2-integrity-constraint-warning/m-p/461815#M14343</link>
      <description>&lt;P&gt;Doesn’t this mean the records you’re trying to insert, the 38 employee IDs, are already in the table?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;BLOCKQUOTE&gt;&lt;HR /&gt;&lt;a href="https://communities.sas.com/t5/user/viewprofilepage/user-id/8409"&gt;@Babloo&lt;/a&gt; wrote:&lt;BR /&gt;
&lt;P&gt;I've DI job which loads data to the physical table via SCD type-2 transformation. When I ran the job I received an error like&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;EM&gt;"WARNING: Add/Update failed for data set INS.EMPLOYEE because data value(s) do not comply with integrity constraint PRIM_KEY. (Occurred 38 times.) NOTE: There were 38 observations read from the data set WORK.ETLS_MATCH. &lt;/EM&gt;&lt;BR /&gt;&lt;EM&gt;NOTE: 0 observations added."&amp;nbsp;&lt;/EM&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Business key for my job is "Employee_ID" and there is no duplicates on &lt;SPAN&gt;Employee_ID&lt;/SPAN&gt;&amp;nbsp;and generated key is "Employee_RK". Could someone you help me understand the likely cause for this issue?&lt;/P&gt;
&lt;HR /&gt;&lt;/BLOCKQUOTE&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sun, 13 May 2018 04:00:11 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Data-Management/SCD-type-2-integrity-constraint-warning/m-p/461815#M14343</guid>
      <dc:creator>Reeza</dc:creator>
      <dc:date>2018-05-13T04:00:11Z</dc:date>
    </item>
    <item>
      <title>Re: SCD type-2 integrity constraint warning</title>
      <link>https://communities.sas.com/t5/SAS-Data-Management/SCD-type-2-integrity-constraint-warning/m-p/461821#M14344</link>
      <description>First: what is the definition of PRIM_KEY?&lt;BR /&gt;Next execute the job with SCD 2 Loader in debug mode, do that you can access the ETLS_MATCH table after execution.</description>
      <pubDate>Sun, 13 May 2018 05:47:18 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Data-Management/SCD-type-2-integrity-constraint-warning/m-p/461821#M14344</guid>
      <dc:creator>LinusH</dc:creator>
      <dc:date>2018-05-13T05:47:18Z</dc:date>
    </item>
    <item>
      <title>Re: SCD type-2 integrity constraint warning</title>
      <link>https://communities.sas.com/t5/SAS-Data-Management/SCD-type-2-integrity-constraint-warning/m-p/461886#M14345</link>
      <description>Could you please help me understand to know how to execute the SCD&lt;BR /&gt;transformation with debug mode?&lt;BR /&gt;</description>
      <pubDate>Sun, 13 May 2018 22:45:37 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Data-Management/SCD-type-2-integrity-constraint-warning/m-p/461886#M14345</guid>
      <dc:creator>Babloo</dc:creator>
      <dc:date>2018-05-13T22:45:37Z</dc:date>
    </item>
    <item>
      <title>Re: SCD type-2 integrity constraint warning</title>
      <link>https://communities.sas.com/t5/SAS-Data-Management/SCD-type-2-integrity-constraint-warning/m-p/461962#M14351</link>
      <description>&lt;P&gt;&lt;a href="https://communities.sas.com/t5/user/viewprofilepage/user-id/8409"&gt;@Babloo&lt;/a&gt;&lt;/P&gt;
&lt;P&gt;The primary key on your target table is {&lt;SPAN&gt;&lt;U&gt;Employee_RK&lt;/U&gt;, &amp;lt;&lt;U&gt;Valid_From_Dttm&lt;/U&gt;&amp;gt;}? Right? &lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;And the Valid_From_Dttm column (or however you call it) contains a SAS Datetime value?&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 14 May 2018 09:30:18 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Data-Management/SCD-type-2-integrity-constraint-warning/m-p/461962#M14351</guid>
      <dc:creator>Patrick</dc:creator>
      <dc:date>2018-05-14T09:30:18Z</dc:date>
    </item>
    <item>
      <title>Re: SCD type-2 integrity constraint warning</title>
      <link>https://communities.sas.com/t5/SAS-Data-Management/SCD-type-2-integrity-constraint-warning/m-p/462149#M14354</link>
      <description>You need to set the macro variable ETLS_DEBUG to something else than 0. Try that in the pre processing for the job, or add it manually in the generated code.&lt;BR /&gt;One option is to set this as default in your server definition. See here for more info:&lt;BR /&gt; &lt;A href="http://documentation.sas.com/?docsetId=etlug&amp;amp;docsetTarget=p0ygtz7di8z8kpn1ufncd1ajt1pj.htm&amp;amp;docsetVersion=4.903&amp;amp;locale=en#p0lanq85qil108n1sptv9ned3zae" target="_blank"&gt;http://documentation.sas.com/?docsetId=etlug&amp;amp;docsetTarget=p0ygtz7di8z8kpn1ufncd1ajt1pj.htm&amp;amp;docsetVersion=4.903&amp;amp;locale=en#p0lanq85qil108n1sptv9ned3zae&lt;/A&gt;</description>
      <pubDate>Mon, 14 May 2018 18:19:10 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Data-Management/SCD-type-2-integrity-constraint-warning/m-p/462149#M14354</guid>
      <dc:creator>LinusH</dc:creator>
      <dc:date>2018-05-14T18:19:10Z</dc:date>
    </item>
  </channel>
</rss>

