<?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: Recovery mechanism in QlikView</title>
    <link>https://community.qlik.com/t5/QlikView/Recovery-mechanism/m-p/640284#M679071</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Use log files to check from which table load the extractor fails and then in your load script restart the extractor from that position where the error comes. Just use exit script command from there and reload the remaining files in the load script and extract remaining files.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Other wise you can use Errormode for extractors&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Eg:-&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class="Bold"&gt;Set ErrorMode = 10;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class="Bold"&gt;Set ErrorMode = 11;&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 20 May 2014 17:01:34 GMT</pubDate>
    <dc:creator>its_anandrjs</dc:creator>
    <dc:date>2014-05-20T17:01:34Z</dc:date>
    <item>
      <title>Recovery mechanism</title>
      <link>https://community.qlik.com/t5/QlikView/Recovery-mechanism/m-p/640283#M679070</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In the following scenario :&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;A .qvw application that extract 100 tables, say after the 60th table load the application crash. Is there a built in recovery mechanism to restart the .qvw but without loading again the tables that got processed successfully. or do I have to implement that mechanism myself. For example using a table (TABLE_NAME, LOAD_OK_OR_NOT) and if then else conditions.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thank you.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 20 May 2014 16:13:10 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Recovery-mechanism/m-p/640283#M679070</guid>
      <dc:creator />
      <dc:date>2014-05-20T16:13:10Z</dc:date>
    </item>
    <item>
      <title>Re: Recovery mechanism</title>
      <link>https://community.qlik.com/t5/QlikView/Recovery-mechanism/m-p/640284#M679071</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Use log files to check from which table load the extractor fails and then in your load script restart the extractor from that position where the error comes. Just use exit script command from there and reload the remaining files in the load script and extract remaining files.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Other wise you can use Errormode for extractors&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Eg:-&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class="Bold"&gt;Set ErrorMode = 10;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN class="Bold"&gt;Set ErrorMode = 11;&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 20 May 2014 17:01:34 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Recovery-mechanism/m-p/640284#M679071</guid>
      <dc:creator>its_anandrjs</dc:creator>
      <dc:date>2014-05-20T17:01:34Z</dc:date>
    </item>
  </channel>
</rss>

