<?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>idea Make failure to parse a redo record an error rather than a warning. in Suggest an Idea</title>
    <link>https://community.qlik.com/t5/Suggest-an-Idea/Make-failure-to-parse-a-redo-record-an-error-rather-than-a/idi-p/1916015</link>
    <description>&lt;P&gt;With and Oracle source, if QLIK fails to parse a redo record it will give a warning rather than an error.&amp;nbsp; However, it will not attempt to resolve the problem or move on.&amp;nbsp; To all outward appearances it will appear the task is still working normally.&amp;nbsp; It will report the latency of the task as the last value of the latency from before the failure with some minor variances.&amp;nbsp; Thus, essentially the task has stopped even attempting to process redo. However, no error was ever reported.&amp;nbsp; The only way to get notified of such an event is to create a notification for all warnings.&amp;nbsp; There is no way within QLIK to filter what warnings will be sent.&amp;nbsp; So, currently QLIK recommend's creating email rules in your email account to filter out all the unnecessary warnings.&amp;nbsp; This would have to be done individually by each user that will get the warning notifications.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Please make a failure to parse a redo record an error rather than a warning so it can be handled more effectively.&lt;/P&gt;</description>
    <pubDate>Tue, 28 Jun 2022 16:21:50 GMT</pubDate>
    <dc:creator>pettitsd</dc:creator>
    <dc:date>2022-06-28T16:21:50Z</dc:date>
    <item>
      <title>From now on, please track this idea from the Ideation por...</title>
      <link>https://community.qlik.com/t5/Suggest-an-Idea/Make-failure-to-parse-a-redo-record-an-error-rather-than-a/idc-p/2100588#M13844</link>
      <description>&lt;P&gt;From now on, please track this idea from the Ideation portal.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;&lt;A title="Link to new idea" href="https://ideation.qlik.com/app/#/case/281666" target="_blank" rel="noopener"&gt;Link to new idea&lt;/A&gt;&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;Meghann&lt;/P&gt;&lt;P data-unlink="true"&gt;&lt;EM&gt;NOTE: Upon clicking this link 2 tabs may open - please feel free to close the one with a login page. If you &lt;STRONG&gt;only&lt;/STRONG&gt; see 1 tab with the login page, please try clicking this link first: &lt;STRONG&gt;&lt;A title="Authenticate me!" href="#" target="_blank" rel="noopener"&gt;Authenticate me!&lt;/A&gt;&lt;/STRONG&gt;&amp;nbsp;t&lt;/EM&gt;&lt;EM&gt;hen try the link above again. Ensure pop-up blocker is off.&lt;/EM&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 02 Aug 2023 15:42:20 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Suggest-an-Idea/Make-failure-to-parse-a-redo-record-an-error-rather-than-a/idc-p/2100588#M13844</guid>
      <dc:creator>Meghann_MacDonald</dc:creator>
      <dc:date>2023-08-02T15:42:20Z</dc:date>
    </item>
    <item>
      <title>Re: Make failure to parse a redo record an error rather than a warning. - Status changed to: Closed - Archived</title>
      <link>https://community.qlik.com/t5/Suggest-an-Idea/Make-failure-to-parse-a-redo-record-an-error-rather-than-a/idc-p/2100589#M13845</link>
      <description />
      <pubDate>Wed, 02 Aug 2023 15:42:22 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Suggest-an-Idea/Make-failure-to-parse-a-redo-record-an-error-rather-than-a/idc-p/2100589#M13845</guid>
      <dc:creator>Ideation</dc:creator>
      <dc:date>2023-08-02T15:42:22Z</dc:date>
    </item>
  </channel>
</rss>

