<?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: Reload a suspended table (logstream as source) in Qlik Replicate</title>
    <link>https://community.qlik.com/t5/Qlik-Replicate/Reload-a-suspended-table-logstream-as-source/m-p/1947423#M3009</link>
    <description>&lt;P&gt;Hi @&lt;SPAN style="background-color:rgba(0,0,0,0.1);color:rgb(46,46,46);font-size:13px;"&gt;&lt;STRONG&gt;rmartinezdezayas,&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Source --&amp;gt; LS &amp;nbsp;(Only changed will be replicated)&lt;/P&gt;
&lt;P&gt;LS --&amp;gt; Target (Redshift) (FULL LOAD from direct source and changes from LS audit files)&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;If you have a table suspended in the Child\Replicate task then just reload the table in the Child\Replicate task is enough and no need to perform any activity on the Logstream task.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks,&lt;/P&gt;
&lt;P&gt;Swathi&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Thu, 23 Jun 2022 13:56:56 GMT</pubDate>
    <dc:creator>SwathiPulagam</dc:creator>
    <dc:date>2022-06-23T13:56:56Z</dc:date>
    <item>
      <title>Reload a suspended table (logstream as source)</title>
      <link>https://community.qlik.com/t5/Qlik-Replicate/Reload-a-suspended-table-logstream-as-source/m-p/1947281#M3007</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;How does reloading a suspended table works?&lt;/P&gt;
&lt;P&gt;This is my scenario:&lt;BR /&gt;I have a &lt;STRONG&gt;logstream task&lt;/STRONG&gt; with source endpoint SAP Application DB and target endpoint the log stream. Then &lt;STRONG&gt;another task&lt;/STRONG&gt; with the source as the log stream and as target Redshift.&lt;BR /&gt;&lt;SPAN&gt;&lt;STRONG&gt;SAP Application DB &amp;gt;&amp;gt; Log Stream &amp;gt;&amp;gt; Redshift&lt;/STRONG&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;SPAN&gt;I store the logs on the Logstream for a larger time that the time SAP source endpoint stores it on its server. So I have more control over it. And I use the __ct tables for change tracking.&lt;BR /&gt;&lt;/SPAN&gt;&lt;SPAN&gt;When a delete statement does not affect any row in the target table, the table is suspended. &lt;BR /&gt;I can't avoid table suspension due to parallelizing apply changes on target. So, general error policy is not available to me and the task policy can only suspend table (I can't ignore the record).&lt;/SPAN&gt;&lt;SPAN&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;My question is: &lt;BR /&gt;When a table is suspended for example because of a delete statement, and I reload it. The table is full loaded even if the log stream task has not been reloaded? Usually a full load of the log stream task and then of the task replicating changes to redshift will reload the entire table, but it is needed? If I reload the table suspended, no rows will be missing, it will be exactly equal to the source table and then star applying changes? Or do I need to reload also the losgtream task?&lt;/P&gt;
&lt;P&gt;I can't test this on my current environment right now, that's why Im asking.&lt;/P&gt;</description>
      <pubDate>Thu, 23 Jun 2022 09:47:52 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Qlik-Replicate/Reload-a-suspended-table-logstream-as-source/m-p/1947281#M3007</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2022-06-23T09:47:52Z</dc:date>
    </item>
    <item>
      <title>Re: Reload a suspended table (logstream as source)</title>
      <link>https://community.qlik.com/t5/Qlik-Replicate/Reload-a-suspended-table-logstream-as-source/m-p/1947423#M3009</link>
      <description>&lt;P&gt;Hi @&lt;SPAN style="background-color:rgba(0,0,0,0.1);color:rgb(46,46,46);font-size:13px;"&gt;&lt;STRONG&gt;rmartinezdezayas,&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Source --&amp;gt; LS &amp;nbsp;(Only changed will be replicated)&lt;/P&gt;
&lt;P&gt;LS --&amp;gt; Target (Redshift) (FULL LOAD from direct source and changes from LS audit files)&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;If you have a table suspended in the Child\Replicate task then just reload the table in the Child\Replicate task is enough and no need to perform any activity on the Logstream task.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks,&lt;/P&gt;
&lt;P&gt;Swathi&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 23 Jun 2022 13:56:56 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Qlik-Replicate/Reload-a-suspended-table-logstream-as-source/m-p/1947423#M3009</guid>
      <dc:creator>SwathiPulagam</dc:creator>
      <dc:date>2022-06-23T13:56:56Z</dc:date>
    </item>
    <item>
      <title>Re: Reload a suspended table (logstream as source)</title>
      <link>https://community.qlik.com/t5/Qlik-Replicate/Reload-a-suspended-table-logstream-as-source/m-p/1947450#M3012</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;unfortunately&lt;SPAN&gt;&amp;nbsp;the only way to resume from a suspended table is to reload.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;what i think you can can try to do is to create a separate task just for this table and start from timestamp.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;Thanks&lt;/P&gt;
&lt;P&gt;Lyka&lt;/P&gt;</description>
      <pubDate>Thu, 23 Jun 2022 14:19:08 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Qlik-Replicate/Reload-a-suspended-table-logstream-as-source/m-p/1947450#M3012</guid>
      <dc:creator>lyka</dc:creator>
      <dc:date>2022-06-23T14:19:08Z</dc:date>
    </item>
  </channel>
</rss>

