<?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: Oracle message repeats over and over but task does not stop in Qlik Replicate</title>
    <link>https://community.qlik.com/t5/Qlik-Replicate/Oracle-message-repeats-over-and-over-but-task-does-not-stop/m-p/2535338#M15419</link>
    <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://community.qlik.com/t5/user/viewprofilepage/user-id/214271"&gt;@MoeE&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;This is informational message as This internal&lt;SPAN&gt;&amp;nbsp;parameter&amp;nbsp;&lt;/SPAN&gt;&lt;FONT color="#339966"&gt;&lt;STRONG&gt;supportResetLog&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/FONT&gt;&lt;SPAN&gt;is currently set to true. When a failover happens, the redo log ID will be reset to zero.&lt;/SPAN&gt;&lt;/P&gt;
&lt;UL class="lia-list-style-type-circle"&gt;
&lt;LI&gt;With&amp;nbsp;&lt;FONT color="#339966"&gt;&lt;STRONG&gt;supportResetLog&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/FONT&gt;set to&amp;nbsp;&lt;FONT color="#339966"&gt;&lt;STRONG&gt;true&lt;/STRONG&gt;&lt;/FONT&gt;, Qlik Replicate will search from zero when it cannot find the next redo log.&lt;/LI&gt;
&lt;LI&gt;With&amp;nbsp;&lt;FONT color="#339966"&gt;&lt;STRONG&gt;supportResetLog&lt;/STRONG&gt;&lt;/FONT&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;set to&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;FONT color="#339966"&gt;&lt;STRONG&gt;false&lt;/STRONG&gt;&lt;/FONT&gt;, Qlik Replicate will keep searching for the next redo log until it appears or the task times out.&amp;nbsp;&lt;EM&gt;This setting resolved the "&lt;/EM&gt;&lt;EM&gt;Start processing new RESETLOGS_ID 'xxxxxxxxx' that does not still have archived Redo logs" error.&amp;nbsp;&lt;/EM&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;&lt;EM&gt;Its depend upon the version used if you are above 2023.5 the this parameter is true by default.&amp;nbsp;&lt;/EM&gt;&lt;/P&gt;
&lt;P&gt;&lt;EM&gt;Regards,&lt;/EM&gt;&lt;/P&gt;
&lt;P&gt;&lt;EM&gt;Sushil kumar&lt;/EM&gt;&lt;/P&gt;</description>
    <pubDate>Wed, 05 Nov 2025 06:44:13 GMT</pubDate>
    <dc:creator>SushilKumar</dc:creator>
    <dc:date>2025-11-05T06:44:13Z</dc:date>
    <item>
      <title>Oracle message repeats over and over but task does not stop</title>
      <link>https://community.qlik.com/t5/Qlik-Replicate/Oracle-message-repeats-over-and-over-but-task-does-not-stop/m-p/2535332#M15418</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I need assistance with this behaviour. A client's task from Oracle on-prem to an Oracle target has been seeing these messages appear in the task logs over and over for the past week:&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;[SOURCE_CAPTURE  ]I:  Start processing new RESETLOGS_ID '1206133529' that does not still have archived Redo logs&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The task does not fail or warn of any issues with the task. The supportResetLog internal parameter is already disabled on the source endpoint.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The main question here is - Why doe the task not notify of any issue or warning, and why does it not fail?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Assistance is appreciated. Thank you.&lt;/P&gt;&lt;P&gt;Kind regards,&lt;/P&gt;&lt;P&gt;Mohammed&lt;/P&gt;</description>
      <pubDate>Wed, 05 Nov 2025 05:40:43 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Qlik-Replicate/Oracle-message-repeats-over-and-over-but-task-does-not-stop/m-p/2535332#M15418</guid>
      <dc:creator>MoeE</dc:creator>
      <dc:date>2025-11-05T05:40:43Z</dc:date>
    </item>
    <item>
      <title>Re: Oracle message repeats over and over but task does not stop</title>
      <link>https://community.qlik.com/t5/Qlik-Replicate/Oracle-message-repeats-over-and-over-but-task-does-not-stop/m-p/2535338#M15419</link>
      <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://community.qlik.com/t5/user/viewprofilepage/user-id/214271"&gt;@MoeE&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;This is informational message as This internal&lt;SPAN&gt;&amp;nbsp;parameter&amp;nbsp;&lt;/SPAN&gt;&lt;FONT color="#339966"&gt;&lt;STRONG&gt;supportResetLog&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/FONT&gt;&lt;SPAN&gt;is currently set to true. When a failover happens, the redo log ID will be reset to zero.&lt;/SPAN&gt;&lt;/P&gt;
&lt;UL class="lia-list-style-type-circle"&gt;
&lt;LI&gt;With&amp;nbsp;&lt;FONT color="#339966"&gt;&lt;STRONG&gt;supportResetLog&lt;/STRONG&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;/FONT&gt;set to&amp;nbsp;&lt;FONT color="#339966"&gt;&lt;STRONG&gt;true&lt;/STRONG&gt;&lt;/FONT&gt;, Qlik Replicate will search from zero when it cannot find the next redo log.&lt;/LI&gt;
&lt;LI&gt;With&amp;nbsp;&lt;FONT color="#339966"&gt;&lt;STRONG&gt;supportResetLog&lt;/STRONG&gt;&lt;/FONT&gt;&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;set to&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;&lt;FONT color="#339966"&gt;&lt;STRONG&gt;false&lt;/STRONG&gt;&lt;/FONT&gt;, Qlik Replicate will keep searching for the next redo log until it appears or the task times out.&amp;nbsp;&lt;EM&gt;This setting resolved the "&lt;/EM&gt;&lt;EM&gt;Start processing new RESETLOGS_ID 'xxxxxxxxx' that does not still have archived Redo logs" error.&amp;nbsp;&lt;/EM&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;&lt;EM&gt;Its depend upon the version used if you are above 2023.5 the this parameter is true by default.&amp;nbsp;&lt;/EM&gt;&lt;/P&gt;
&lt;P&gt;&lt;EM&gt;Regards,&lt;/EM&gt;&lt;/P&gt;
&lt;P&gt;&lt;EM&gt;Sushil kumar&lt;/EM&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 05 Nov 2025 06:44:13 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Qlik-Replicate/Oracle-message-repeats-over-and-over-but-task-does-not-stop/m-p/2535338#M15419</guid>
      <dc:creator>SushilKumar</dc:creator>
      <dc:date>2025-11-05T06:44:13Z</dc:date>
    </item>
  </channel>
</rss>

