Internal inconsistency type D error only when performing partial reload
Hi all,
Couple of our Qlikview applications have started giving us 'internal inconsistency, type D' errors every time partial reload is performed since the QVD file they are loading from has grown quite big. The applications read data from QVD files, initially one big reload reading from a quite big QVD file (125M currently), then small, partial reloads from daily QVD files which are very small. When reload is performed, there is no problem. When partial reload is performed, it gives that error every time.
I assume this is due to the fact that when partial reload is performed, the original load needs to be kept in memory and the new data needs to be 'appended' to it. The strange thing is, that the same applications with same QVD files run fine on my PC, but only have this problem running on the server. My PC has less RAM and processing power than the server and the server also has Qlikview Server 9.0 SR3 installed and that's the only difference I can think of. These applications are run using Qlikview x64 application, they are not run through the server or management console.
Is there a setting somewhere on the server that puts certain limits on amount of data that can be kept in memory? I know we have more than enough RAM and the fact that it runs on my PC makes me think that just installing more RAM is not going to solve the problem - it is some environmental issue or a setting somewhere. I've tried stopping all Qlikview services then running the application (in case there was an issue with some service running), but still have the same problem.
I've noticed few posts relating to 'internal inconsistency' errors and I think the causes are possibly different, but has anybody ever got to the bottom of this? Any thoughts are appreciated..
Here is what Qliktech recomends on internal inconsitency errors.
The internal inconsistency errors are mere pointers to access violations in memory, and are treated as bugs when and if reproduced. Send the application and steps to reproduce to Qliktech Support.
No help so far. However... I un-installed that version of Qlikview (64 bit application, SR3) and installed the one from my PC (32 bit, version 9, no SR) and guess what - it works just fine.
I still have an oustanding question with the support and they promised to look into it next week, so if I get any resolution, I'll post it here.
I just looked at a case with the same issue as this. We've confirmed that a memory allocation issue seems to happen in a case with partial reloads, which signals an Internal inconsistency warning. We've sent the data further for analysis and confirmation. The bug id for this issue is #27071.
I'm having a similar problem while doing a binary load with a concatenation. It's the same build of QlikView (v9 SR3 x64). Receive the same "Internal inconsistency, type D" warning and the application crashes on the server.
I guess you mean that the task crashes when trying to reload the document, correct?
The bug about partial reloads failing (#27071) with this error is still under investigation, and will unfortunately not make it into SR4 as it looks now.
