Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hi friends,
I have QlikView project and if start "Reload" function for restore data from data source (local MySQL database) it reached following error:
SQL Error:[MySQL][ODBC 5.1 Driver][mysqld-5.0.67-community-nt]MySQL client ran out of memory
SQL Scriptline:
SQL State:S1000
VydajTovaruNaPredajniPodlaPartnera:
SQL SELECT CisloPredajne,
CisloKarty,
NC,PC,KS
CisloPartneraMO,
DatumDokladu
FROM milkagro.vydaj
This table has 467MB of data. I have similar MySQL table TAB2 with the same structure but only 40MB of data and that QV reloaded in order.
What tip for running reload for that huge amount of data?
Hi,
I had the same issue on my dev machine. I am no QV expert nor poweruser but to me it seems it is actually an ODBC error, not related to QV.
What worked for me was to go to the ODBC details screen,
1. open ODBC data source admin
2. click configure on the datasource you use
3. click details
4. go to tab 'connection' and check "allow big result sets"
5. go to tab 'cursor/results' and check 'don't cache results'
This allowed me to get past the out-of-memory error...
hello,
I have the same error, can you please tell me how you have resolve this probleme?
I am assuming that your server has bigger capacity than your developer PC and that it has memory large enough to handle your data. If that is the case, go to debugger, run a limited load of say 10 rows, save the local file & then copy this qvw to your server & then reload in server.
Dinesh.
Same Problem here with a Mysql server we have a 32GB machine but not even 20GB are consumed when the error appears:
SQL Error:[MySQL][ODBC 5.1 Driver][mysqld-5.0.67-community-nt]MySQL client ran out of memory
and it always is reproduced with the same table od the DB.
Anyone has a solution for this?
Hi,
I had the same issue on my dev machine. I am no QV expert nor poweruser but to me it seems it is actually an ODBC error, not related to QV.
What worked for me was to go to the ODBC details screen,
1. open ODBC data source admin
2. click configure on the datasource you use
3. click details
4. go to tab 'connection' and check "allow big result sets"
5. go to tab 'cursor/results' and check 'don't cache results'
This allowed me to get past the out-of-memory error...
This worked for me. Thanks.