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

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

Wed, 21 Apr 2010 07:29:12 GMT

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.

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

Tue, 24 Aug 2010 09:56:58 GMT

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.

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

Tue, 24 Aug 2010 10:03:16 GMT

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

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

Tue, 24 Aug 2010 10:10:12 GMT

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?

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

Anonymous — Tue, 24 Aug 2010 10:31:08 GMT

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

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

Tue, 24 Aug 2010 10:41:56 GMT

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.

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

Tue, 24 Aug 2010 10:42:43 GMT

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.

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

montubhardwaj — Tue, 24 Aug 2010 14:08:08 GMT

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

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

jonathandienst — Tue, 24 Aug 2010 15:11:09 GMT

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.

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

Tue, 22 Feb 2011 09:12:54 GMT

Hi,

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

Thanks

Ferran

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

suniljain — Tue, 22 Feb 2011 09:36:59 GMT

Dear Rikab,

one alternative is you can increase virrual memory of your server.

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

Tue, 22 Feb 2011 09:49:31 GMT

Hi,

I have no problem with the memory, my server has 54 GB. The thing is that QVS starts to 5 GB and can increase to 32 GB in an hour. So, no matter how much memory I have, the problem is with the document I guess. This is my table schema

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

Fri, 23 Sep 2011 04:08:12 GMT

Hi,

I had this error earliar. When I was debug my data, I had a specail character(") in the data. So I just removed and tried , it was working fine.

The error message is totally different from the error. One small advantage is , the Qlikview stops the particular row number when the row has special character.

Hope, this will help.

Thanks

Thiya

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

Fri, 28 Dec 2012 20:24:30 GMT

If your model is going to grow beyond the 5Gb limit while reloading, you have to use the 64-bit version of QV. (obviously also requires a 64-bit operating system...)