Qlik Community

QlikView App Development

Discussion Board for collaboration related to QlikView App Development.

Announcements
QlikWorld, June 24-25, 2020. Free virtual event for DI and DA gurus. Register Today
cancel
Showing results for 
Search instead for 
Did you mean: 
Highlighted
Not applicable

Out OF VIRTUAL AND/OR LOGICAL MEMORY, allocating 2 MB

Hi All,

This document was seems to be working at some point of time before. But after I opened all the tables in from the document(New Sheet Object --> Table Box) one by one. After that if I select any rows or then press the clear button I am getting the following error. Why is that happening? Is there is any other way to find how much usage is left out in the qlikview application according to my system memory.

Previous I was thinking that this all is happening only due to synthetic keys now i feel there are something else with which it can affect the document.

I have so many documents that have been downloaded in my system. I believe it will not affect the qlikview memory. But following errors comes at some point of time in qlikview. Which is really irritating.

error loading image

13 Replies
Highlighted
Not applicable

Out OF VIRTUAL AND/OR LOGICAL MEMORY, allocating 2 MB

Hi Rikab

Did u manage to fx this problem? im having a similar one. when i reload the data from the script i get the same message. My machine is 4GB RAM and there are no synthetic tables.

Highlighted
Not applicable

Out OF VIRTUAL AND/OR LOGICAL MEMORY, allocating 2 MB

They said it doesn't matter how much RAM you have in your machine. What matter's is how much much memory is available at that point of time. So many times in one of my document I used to get these kinds of memory related error. But once I logs off and reload the document there was no memory related error.

There is so specific solution provided by anyone for these types of issue

Highlighted
Not applicable

Out OF VIRTUAL AND/OR LOGICAL MEMORY, allocating 2 MB

well that sux. My document does it as i bot up my PC. even if i log off it does the same thing. Any deas?

Highlighted
Specialist
Specialist

Out OF VIRTUAL AND/OR LOGICAL MEMORY, allocating 2 MB

You could try setting the calculation memory higher etc ... (this can be done on general level i thought and also on report level in the QEMC and QMC) ...

rgrds

Highlighted
Not applicable

Out OF VIRTUAL AND/OR LOGICAL MEMORY, allocating 2 MB

I kinda got the error fixed but it still occurs a bt further on after the reload when i add more information. all i did was i went to properties on My computer----->advanced tab------>Settings under performance------>advanced------->and i realocated more virtual memory to the PC. It worked the first time i reloaded but then a lil down the line when i reloaded more information into the document the same error came up.

Highlighted
Not applicable

Out OF VIRTUAL AND/OR LOGICAL MEMORY, allocating 2 MB

Yes it is! I used to get these kinds of memory related error message. Not even once I got the solution. Even once strange thing happened. One of the document got the above message though I have 4gb ram But the same document when I tried to open another system which also have 4gb ram there is no such kind of memory related error message.

So what I can suggest is try to open your document from some other machine which which also has 4gm ram. If it open up there without any issues then report it to qlikview support. But I am sure they will tell that it depends upon the currently available memory in your machine. Check with them and let me know too.

Highlighted
Specialist
Specialist

Out OF VIRTUAL AND/OR LOGICAL MEMORY, allocating 2 MB

Hi Rikab,

Possibly, You can try increasing the memory allocated to the objects. Try doing as below and this might help you out:

Go to Settings--> User Preferences --> Objects and Uncheck the option "Ignore calculation limits" and increase the memory allocated.

Please see the attached below:

Cheers,

Sharma

Highlighted
MVP
MVP

Out OF VIRTUAL AND/OR LOGICAL MEMORY, allocating 2 MB

This problem can also be caused by a model design that has two or more large tables not connected by any key, and an expression that uses fields from both tables.

This causes QV to do an implicit cross-join (outer join/cartesian join) between the tables to generate the results.

So, if you have 2 tables with 100,000 rows in each, no common key and an expression that uses fields from both, QV will try to generate space for 10,000,000,000 (10 billion) records for the calculation. You can easily see how that will eat through whatever memory you throw at it (unless you are using x64 with about a terabyte of RAM!)

Hope this helps

Jonathan

Disclaimer: I don't know for sure exactly how QV handles the internals of such a scenario. This is based on how I expect it to be done and after fixing the same problem the OP is experiencing. Smile

Logic will get you from a to b. Imagination will take you everywhere. - A Einstein
Highlighted
Not applicable

Out OF VIRTUAL AND/OR LOGICAL MEMORY, allocating 2 MB

Hi,

I'm having this problem, how can avoid the memory eating? I need those tables...

Thanks

Ferran