<?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 Server 9 SR2 Internal inconsistency, Type D detected in QlikView</title>
    <link>https://community.qlik.com/t5/QlikView/Server-9-SR2-Internal-inconsistency-Type-D-detected/m-p/175501#M1311499</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Now then,&lt;/P&gt;&lt;P&gt;I am currently testing using autonumber() as my key fields to find out if the performance will increase significantly from a concatenated key. After making the changes and reloading the script, I am experiencing inconsistent type D errors. This will stop displaying the data and will make the file corrupt ?&lt;/P&gt;&lt;P&gt;I have to close qlikview and restart services for qlikview to function properly again. A recovery file is not created for the corrupt file. If i open the corrupt file, I get the inconsistent message again!&lt;/P&gt;&lt;P&gt;The table joins are creating 150 million rows of data which creates a 6Gb file once saved. This is the reason why i was going to try using autonumber as performance is increased testing with smaller files.&lt;/P&gt;&lt;P&gt;Any ideas anybody?&lt;/P&gt;&lt;P&gt;Its definately not a server issue as it is 64 bit 133Gb memory and has 24 core cpu&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 26 Jan 2026 18:19:17 GMT</pubDate>
    <dc:creator />
    <dc:date>2026-01-26T18:19:17Z</dc:date>
    <item>
      <title>Server 9 SR2 Internal inconsistency, Type D detected</title>
      <link>https://community.qlik.com/t5/QlikView/Server-9-SR2-Internal-inconsistency-Type-D-detected/m-p/175501#M1311499</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Now then,&lt;/P&gt;&lt;P&gt;I am currently testing using autonumber() as my key fields to find out if the performance will increase significantly from a concatenated key. After making the changes and reloading the script, I am experiencing inconsistent type D errors. This will stop displaying the data and will make the file corrupt ?&lt;/P&gt;&lt;P&gt;I have to close qlikview and restart services for qlikview to function properly again. A recovery file is not created for the corrupt file. If i open the corrupt file, I get the inconsistent message again!&lt;/P&gt;&lt;P&gt;The table joins are creating 150 million rows of data which creates a 6Gb file once saved. This is the reason why i was going to try using autonumber as performance is increased testing with smaller files.&lt;/P&gt;&lt;P&gt;Any ideas anybody?&lt;/P&gt;&lt;P&gt;Its definately not a server issue as it is 64 bit 133Gb memory and has 24 core cpu&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 26 Jan 2026 18:19:17 GMT</pubDate>
      <guid>https://community.qlik.com/t5/QlikView/Server-9-SR2-Internal-inconsistency-Type-D-detected/m-p/175501#M1311499</guid>
      <dc:creator />
      <dc:date>2026-01-26T18:19:17Z</dc:date>
    </item>
  </channel>
</rss>

