<?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>article Qlik Replicate: DEFAULT_FILE_NOT_FOUND Error in Official Support Articles</title>
    <link>https://community.qlik.com/t5/Official-Support-Articles/Qlik-Replicate-DEFAULT-FILE-NOT-FOUND-Error/ta-p/2474691</link>
    <description>&lt;P&gt;Qlik has observed the following error while working with Databricks Delta Lakehouse endpoint in Replicate 2023.05 or above. This Technical Advisory article aims to create awareness of the issue and provides a workaround.&amp;nbsp;&lt;/P&gt;
&lt;P class="lia-indent-padding-left-30px"&gt;&lt;FONT face="courier new,courier"&gt;&lt;SPAN&gt;[DEFAULT_FILE_NOT_FOUND] It is possible the underlying files have been updated. You can explicitly invalidate the cache in Spark by running 'REFRESH TABLE tableName' command in SQL or by recreating the Dataset/DataFrame involved. If disk cache is stale or the underlying files have been removed, you can invalidate disk cache manually by restarting the cluster.&lt;/SPAN&gt;&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;This causes the table to be suspended and requires a reload.&lt;/P&gt;
&lt;H4&gt;&lt;BR /&gt;&lt;FONT color="#339966"&gt;&lt;SPAN&gt;&lt;STRONG&gt;Environment:&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;/FONT&gt;&lt;/H4&gt;
&lt;UL&gt;
&lt;LI&gt;Qlik Replicate 2023.05 and later&lt;/LI&gt;
&lt;/UL&gt;
&lt;H3&gt;&lt;FONT color="#339966"&gt;&lt;STRONG&gt;Resolution&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/H3&gt;
&lt;H4&gt;&lt;FONT color="#339966"&gt;&lt;STRONG&gt;Fix Version:&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/H4&gt;
&lt;P class="lia-indent-padding-left-30px"&gt;A fix is currently being worked on and patches will be made available at the earliest.&lt;/P&gt;
&lt;H4&gt;&lt;FONT color="#339966"&gt;&lt;STRONG&gt;Workaround:&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/H4&gt;
&lt;OL&gt;
&lt;LI&gt;Go to the &lt;STRONG&gt;Databricks Endpoint&lt;/STRONG&gt;&lt;/LI&gt;
&lt;LI&gt;Open the&amp;nbsp;&lt;STRONG&gt;Advanced&amp;nbsp;&lt;/STRONG&gt;tab&lt;/LI&gt;
&lt;LI&gt;Open&amp;nbsp;&lt;STRONG&gt;Internal Paramters&lt;/STRONG&gt;&lt;/LI&gt;
&lt;LI&gt;Add the parameter: &lt;STRONG&gt;additionalConnectionProperties&lt;/STRONG&gt;&lt;/LI&gt;
&lt;LI&gt;Set the value to&lt;STRONG&gt;ForceSynchronousExec=1&lt;BR /&gt;&lt;BR /&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="additionalConnectionProperties.png" style="width: 590px;"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/170244i995BEE6FE132D6D1/image-size/large?v=v2&amp;amp;px=999" role="button" title="additionalConnectionProperties.png" alt="additionalConnectionProperties.png" /&gt;&lt;/span&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/STRONG&gt;&lt;/LI&gt;
&lt;LI&gt;Save the Endpoint&lt;/LI&gt;
&lt;LI&gt;Stop and Resume the task&lt;/LI&gt;
&lt;/OL&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;EM&gt;Information provided on this defect is given as is at the time of documenting. For up to date information, please review the most recent Release Notes, or contact support with the ID &lt;STRONG&gt;QB-28166&lt;/STRONG&gt; for reference.&lt;/EM&gt;&lt;/P&gt;
&lt;H3&gt;&lt;FONT color="#339966"&gt;&lt;STRONG&gt;Cause&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/H3&gt;
&lt;P class="lia-indent-padding-left-30px"&gt;Product Defect ID: QB-28166&lt;/P&gt;</description>
    <pubDate>Tue, 06 Aug 2024 05:47:39 GMT</pubDate>
    <dc:creator>shashi_holla</dc:creator>
    <dc:date>2024-08-06T05:47:39Z</dc:date>
    <item>
      <title>Qlik Replicate: DEFAULT_FILE_NOT_FOUND Error</title>
      <link>https://community.qlik.com/t5/Official-Support-Articles/Qlik-Replicate-DEFAULT-FILE-NOT-FOUND-Error/ta-p/2474691</link>
      <description>&lt;P&gt;Qlik has observed the following error while working with Databricks Delta Lakehouse endpoint in Replicate 2023.05 or above. This Technical Advisory article aims to create awareness of the issue and provides a workaround.&amp;nbsp;&lt;/P&gt;
&lt;P class="lia-indent-padding-left-30px"&gt;&lt;FONT face="courier new,courier"&gt;&lt;SPAN&gt;[DEFAULT_FILE_NOT_FOUND] It is possible the underlying files have been updated. You can explicitly invalidate the cache in Spark by running 'REFRESH TABLE tableName' command in SQL or by recreating the Dataset/DataFrame involved. If disk cache is stale or the underlying files have been removed, you can invalidate disk cache manually by restarting the cluster.&lt;/SPAN&gt;&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;This causes the table to be suspended and requires a reload.&lt;/P&gt;
&lt;H4&gt;&lt;BR /&gt;&lt;FONT color="#339966"&gt;&lt;SPAN&gt;&lt;STRONG&gt;Environment:&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;/FONT&gt;&lt;/H4&gt;
&lt;UL&gt;
&lt;LI&gt;Qlik Replicate 2023.05 and later&lt;/LI&gt;
&lt;/UL&gt;
&lt;H3&gt;&lt;FONT color="#339966"&gt;&lt;STRONG&gt;Resolution&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/H3&gt;
&lt;H4&gt;&lt;FONT color="#339966"&gt;&lt;STRONG&gt;Fix Version:&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/H4&gt;
&lt;P class="lia-indent-padding-left-30px"&gt;A fix is currently being worked on and patches will be made available at the earliest.&lt;/P&gt;
&lt;H4&gt;&lt;FONT color="#339966"&gt;&lt;STRONG&gt;Workaround:&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/H4&gt;
&lt;OL&gt;
&lt;LI&gt;Go to the &lt;STRONG&gt;Databricks Endpoint&lt;/STRONG&gt;&lt;/LI&gt;
&lt;LI&gt;Open the&amp;nbsp;&lt;STRONG&gt;Advanced&amp;nbsp;&lt;/STRONG&gt;tab&lt;/LI&gt;
&lt;LI&gt;Open&amp;nbsp;&lt;STRONG&gt;Internal Paramters&lt;/STRONG&gt;&lt;/LI&gt;
&lt;LI&gt;Add the parameter: &lt;STRONG&gt;additionalConnectionProperties&lt;/STRONG&gt;&lt;/LI&gt;
&lt;LI&gt;Set the value to&lt;STRONG&gt;ForceSynchronousExec=1&lt;BR /&gt;&lt;BR /&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="additionalConnectionProperties.png" style="width: 590px;"&gt;&lt;img src="https://community.qlik.com/t5/image/serverpage/image-id/170244i995BEE6FE132D6D1/image-size/large?v=v2&amp;amp;px=999" role="button" title="additionalConnectionProperties.png" alt="additionalConnectionProperties.png" /&gt;&lt;/span&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;/STRONG&gt;&lt;/LI&gt;
&lt;LI&gt;Save the Endpoint&lt;/LI&gt;
&lt;LI&gt;Stop and Resume the task&lt;/LI&gt;
&lt;/OL&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;EM&gt;Information provided on this defect is given as is at the time of documenting. For up to date information, please review the most recent Release Notes, or contact support with the ID &lt;STRONG&gt;QB-28166&lt;/STRONG&gt; for reference.&lt;/EM&gt;&lt;/P&gt;
&lt;H3&gt;&lt;FONT color="#339966"&gt;&lt;STRONG&gt;Cause&lt;/STRONG&gt;&lt;/FONT&gt;&lt;/H3&gt;
&lt;P class="lia-indent-padding-left-30px"&gt;Product Defect ID: QB-28166&lt;/P&gt;</description>
      <pubDate>Tue, 06 Aug 2024 05:47:39 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Official-Support-Articles/Qlik-Replicate-DEFAULT-FILE-NOT-FOUND-Error/ta-p/2474691</guid>
      <dc:creator>shashi_holla</dc:creator>
      <dc:date>2024-08-06T05:47:39Z</dc:date>
    </item>
  </channel>
</rss>

