<?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: Qlik Replicate with  Informix as source and full load with transactions on in Qlik Replicate</title>
    <link>https://community.qlik.com/t5/Qlik-Replicate/Qlik-Replicate-with-Informix-as-source-and-full-load-with/m-p/2548291#M16228</link>
    <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://community.qlik.com/t5/user/viewprofilepage/user-id/182107"&gt;@lguevara&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;
&lt;P data-end="71" data-start="0"&gt;Feel free to let us know whether the above workaround meets your needs.&lt;/P&gt;
&lt;P data-end="122" data-start="73"&gt;If not, here are a couple of alternative options:&lt;/P&gt;
&lt;P data-end="437" data-start="124"&gt;&lt;STRONG data-end="213" data-start="124"&gt;Option 1 – Have &lt;SPAN class="hover:entity-accent entity-underline inline cursor-pointer align-baseline"&gt;&lt;SPAN class="whitespace-normal"&gt;Qlik Replicate&lt;/SPAN&gt;&lt;/SPAN&gt; wait when locks are encountered&lt;/STRONG&gt;&lt;BR data-end="216" data-start="213" /&gt;&amp;nbsp; &amp;nbsp; In Informix source endpoint adding an internal parameter &lt;STRONG&gt;lockWait &lt;/STRONG&gt;(default is 0), setting it to a reasonable value (for example, 120 seconds). This allows Replicate to wait 2 minutes for open transactions to close before proceeding, if hits locks.&lt;/P&gt;
&lt;P data-is-only-node="" data-is-last-node="" data-end="672" data-start="439"&gt;&lt;STRONG data-end="471" data-start="439"&gt;Option 2 – Allow dirty reads&lt;/STRONG&gt;&lt;BR data-end="474" data-start="471" /&gt;&amp;nbsp; &amp;nbsp; Enable dirty reads on the source (&lt;SPAN class="hover:entity-accent entity-underline inline cursor-pointer align-baseline"&gt;&lt;SPAN class="whitespace-normal"&gt;IBM Informix&lt;/SPAN&gt;&lt;/SPAN&gt;). This may result in reading uncommitted or inconsistent data so it is generally not recommended.&lt;/P&gt;
&lt;P&gt;Regards,&lt;/P&gt;
&lt;P&gt;John.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Sat, 02 May 2026 01:25:38 GMT</pubDate>
    <dc:creator>john_wang</dc:creator>
    <dc:date>2026-05-02T01:25:38Z</dc:date>
    <item>
      <title>Qlik Replicate with  Informix as source and full load with transactions on</title>
      <link>https://community.qlik.com/t5/Qlik-Replicate/Qlik-Replicate-with-Informix-as-source-and-full-load-with/m-p/2548206#M16220</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;I have Informix as a source and I want to execute a Full Load, but I notice that there is a restriction: &lt;I&gt;'All transactions should be manually stopped before starting a Full Load task. Transactions started during the Full Load operation will be cached.'&lt;/I&gt;&lt;/P&gt;&lt;P&gt;Since I cannot stop transactions on the source database, what are the recommendations?&lt;/P&gt;&lt;P&gt;thanks.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 30 Apr 2026 14:52:29 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Qlik-Replicate/Qlik-Replicate-with-Informix-as-source-and-full-load-with/m-p/2548206#M16220</guid>
      <dc:creator>lguevara</dc:creator>
      <dc:date>2026-04-30T14:52:29Z</dc:date>
    </item>
    <item>
      <title>Re: Qlik Replicate with  Informix as source and full load with transactions on</title>
      <link>https://community.qlik.com/t5/Qlik-Replicate/Qlik-Replicate-with-Informix-as-source-and-full-load-with/m-p/2548212#M16221</link>
      <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://community.qlik.com/t5/user/viewprofilepage/user-id/182107"&gt;@lguevara&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;
&lt;P data-end="279" data-start="54"&gt;This appears to be a timing issue. For example, when you start a task, it may take around 5 seconds to reach the RUNNING state. If there are no open transactions during that window, the startup should complete without issues.&lt;/P&gt;
&lt;P data-is-only-node="" data-is-last-node="" data-end="404" data-start="281"&gt;If it’s difficult to find a quiet window during business hours, consider starting the task during off-peak periods instead.&lt;/P&gt;
&lt;P data-is-only-node="" data-is-last-node="" data-end="404" data-start="281"&gt;Hope this helps.&lt;/P&gt;
&lt;P data-is-only-node="" data-is-last-node="" data-end="404" data-start="281"&gt;John.&lt;/P&gt;</description>
      <pubDate>Thu, 30 Apr 2026 15:22:59 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Qlik-Replicate/Qlik-Replicate-with-Informix-as-source-and-full-load-with/m-p/2548212#M16221</guid>
      <dc:creator>john_wang</dc:creator>
      <dc:date>2026-04-30T15:22:59Z</dc:date>
    </item>
    <item>
      <title>Re: Qlik Replicate with  Informix as source and full load with transactions on</title>
      <link>https://community.qlik.com/t5/Qlik-Replicate/Qlik-Replicate-with-Informix-as-source-and-full-load-with/m-p/2548291#M16228</link>
      <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://community.qlik.com/t5/user/viewprofilepage/user-id/182107"&gt;@lguevara&lt;/a&gt;&amp;nbsp;,&lt;/P&gt;
&lt;P data-end="71" data-start="0"&gt;Feel free to let us know whether the above workaround meets your needs.&lt;/P&gt;
&lt;P data-end="122" data-start="73"&gt;If not, here are a couple of alternative options:&lt;/P&gt;
&lt;P data-end="437" data-start="124"&gt;&lt;STRONG data-end="213" data-start="124"&gt;Option 1 – Have &lt;SPAN class="hover:entity-accent entity-underline inline cursor-pointer align-baseline"&gt;&lt;SPAN class="whitespace-normal"&gt;Qlik Replicate&lt;/SPAN&gt;&lt;/SPAN&gt; wait when locks are encountered&lt;/STRONG&gt;&lt;BR data-end="216" data-start="213" /&gt;&amp;nbsp; &amp;nbsp; In Informix source endpoint adding an internal parameter &lt;STRONG&gt;lockWait &lt;/STRONG&gt;(default is 0), setting it to a reasonable value (for example, 120 seconds). This allows Replicate to wait 2 minutes for open transactions to close before proceeding, if hits locks.&lt;/P&gt;
&lt;P data-is-only-node="" data-is-last-node="" data-end="672" data-start="439"&gt;&lt;STRONG data-end="471" data-start="439"&gt;Option 2 – Allow dirty reads&lt;/STRONG&gt;&lt;BR data-end="474" data-start="471" /&gt;&amp;nbsp; &amp;nbsp; Enable dirty reads on the source (&lt;SPAN class="hover:entity-accent entity-underline inline cursor-pointer align-baseline"&gt;&lt;SPAN class="whitespace-normal"&gt;IBM Informix&lt;/SPAN&gt;&lt;/SPAN&gt;). This may result in reading uncommitted or inconsistent data so it is generally not recommended.&lt;/P&gt;
&lt;P&gt;Regards,&lt;/P&gt;
&lt;P&gt;John.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sat, 02 May 2026 01:25:38 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Qlik-Replicate/Qlik-Replicate-with-Informix-as-source-and-full-load-with/m-p/2548291#M16228</guid>
      <dc:creator>john_wang</dc:creator>
      <dc:date>2026-05-02T01:25:38Z</dc:date>
    </item>
  </channel>
</rss>

