<?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: Latency in Logstream task in Qlik Replicate</title>
    <link>https://community.qlik.com/t5/Qlik-Replicate/Latency-in-Logstream-task/m-p/2477156#M12424</link>
    <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://community.qlik.com/t5/user/viewprofilepage/user-id/90520"&gt;@suvbin&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;You need to check whether there is any long running transaction at the Oracle side which is not committed yet.&lt;/P&gt;
&lt;P&gt;Replicate will be waiting for the source for the transaction to gets commit so latency will increase. Once transactions get committed, it will transfer the data to the target accordingly.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Regards,&lt;/P&gt;
&lt;P&gt;Suresh&lt;/P&gt;</description>
    <pubDate>Wed, 21 Aug 2024 05:56:25 GMT</pubDate>
    <dc:creator>sureshkumar</dc:creator>
    <dc:date>2024-08-21T05:56:25Z</dc:date>
    <item>
      <title>Latency in Logstream task</title>
      <link>https://community.qlik.com/t5/Qlik-Replicate/Latency-in-Logstream-task/m-p/2477147#M12423</link>
      <description>&lt;P&gt;Hi ,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;We could see latency in the logstream task after some change activity at the source side. more redo logs got generated. Now the task is running behind of 100 to 200 logs. How to make replicate to read faster these redo logs.?&lt;/P&gt;
&lt;P&gt;And also i could see around 24&amp;nbsp; transactions are not committed at source.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Please suggest.&lt;/P&gt;
&lt;P&gt;readahead blocks has been set to 400000&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 21 Aug 2024 04:22:42 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Qlik-Replicate/Latency-in-Logstream-task/m-p/2477147#M12423</guid>
      <dc:creator>suvbin</dc:creator>
      <dc:date>2024-08-21T04:22:42Z</dc:date>
    </item>
    <item>
      <title>Re: Latency in Logstream task</title>
      <link>https://community.qlik.com/t5/Qlik-Replicate/Latency-in-Logstream-task/m-p/2477156#M12424</link>
      <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://community.qlik.com/t5/user/viewprofilepage/user-id/90520"&gt;@suvbin&lt;/a&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;You need to check whether there is any long running transaction at the Oracle side which is not committed yet.&lt;/P&gt;
&lt;P&gt;Replicate will be waiting for the source for the transaction to gets commit so latency will increase. Once transactions get committed, it will transfer the data to the target accordingly.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Regards,&lt;/P&gt;
&lt;P&gt;Suresh&lt;/P&gt;</description>
      <pubDate>Wed, 21 Aug 2024 05:56:25 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Qlik-Replicate/Latency-in-Logstream-task/m-p/2477156#M12424</guid>
      <dc:creator>sureshkumar</dc:creator>
      <dc:date>2024-08-21T05:56:25Z</dc:date>
    </item>
  </channel>
</rss>

