I've 3 GB RAM on my machine but still I'm seeing an error 'OUT OF VIRTUAL MEMORY, allocating 2MB'. Could you please let me know any of the settings might save me. My application size is just 2.5 MB only. It is Win 7 O.S. and will expand the VM based on usage. Please let me know if you guys have any idea. Thanks much for all your time and help!!! - Sasi
I'm guessing that your problem is not in the data size, but in one of the two possible mistakes:
1. You forgot to drop one of the temporary tables, and QlikView is busy building a huge synthetic key at the end of the load.
2. You have data that is not properly linked, and some screen objects that use elements of data that are not linked - in this case, QlikView is busy building a Cartesian table out of your data...
To find out what's wrong, open Debug, and run a limited load of a 100 rows per table. At the end, open your Table Viewer and examine your table structure - do you see any synthetic keys? do you see any data that's not linked?
Oleg, Appreciated for your time and reply on this issue.
I looked into this issue and found that there exists a duplicate object and this data is shown tree view display. I'm really upset why qlikview is not able to handle the duplicate object while loading and also data is not in millions.. its around 4k rows. Sometimes really not getting why this sort of wierd behaviour of the tool. There is no unwanted temp temp or sunthetic key tables.
I have another bulk app of 300 MB and 10 million rows of data, there I've no complaints on the tool behaviour. But the case I've explained above is not that kind.
