topic ODBC timeout in QlikView https://community.qlik.com/t5/QlikView/ODBC-timeout/m-p/157398#M1309778 <HTML><HEAD></HEAD><BODY><P>Few things:</P><P></P><UL><LI>depending on database load, parameter value... some queries might take much longer than 7 minutes</LI><LI>some parameter values might result in invalid SQL . Log the "loop counter" and manually run the query with the last logged value</LI><LI>If you really issue a query every 7 minutes, there cannot be an "idle timeout". But there can be a "total duration timeout", which you can test for . Temporarily put the CONNECT statement inside the loop.</LI></UL><P></P><P>-Alex</P><P></P></BODY></HTML> Mon, 18 Oct 2010 09:48:15 GMT 2010-10-18T09:48:15Z ODBC timeout https://community.qlik.com/t5/QlikView/ODBC-timeout/m-p/157397#M1309776 <HTML><HEAD></HEAD><BODY><P>I wrote a loop that pass parameter into a query. Each iteration takes about 5 to 7 minutes to run. Unfortunately on the 6th hour of the iteration run I got the Qlikview error below. In which case, I have to start the process all over again. Does Qlikview disconnect an ODBC connection after certain amount of time? The qlikview report is connecting to a Onetick database, a time series database.</P><P></P><P>Qlikview Error Message</P><P>10/15/2010 06:04:25.4028017 Information Reloading...<BR />10/15/2010 06:19:25.5590517 Information Reloading....<BR />10/15/2010 06:34:25.9642869 Information Reloading.....<BR />10/15/2010 06:49:25.9535457 Information Reloading......<BR />10/15/2010 07:04:25.9535457 Information Reloading.......<BR />10/15/2010 07:19:25.9535457 Information Reloading........<BR />10/15/2010 07:34:25.9535457 Information Reloading.........<BR />10/15/2010 07:49:25.9535457 Information Reloading..........<BR />10/15/2010 08:04:25.9535457 Information Slowing down logging. LoggingSeconds=1200<BR />10/15/2010 08:04:25.9535457 Information Reloading<BR />10/15/2010 08:21:00.4379207 Error Aborting Reload. Error=QDSMain.TaskResult<BR />10/15/2010 08:21:10.2347957 Warning The QlikView Engine is Reloading, it will be killed (Please ignore logged warnings/errors about the kill).<BR />10/15/2010 08:21:10.2347957 Information Killing the QlikView Engine. ProcessID=4280<BR />10/15/2010 08:21:10.3441707 Information Closed the QlikView Engine successfully. ProcessID=4280<BR />10/15/2010 08:21:10.3441707 Error Reload was aborted.<BR />10/15/2010 08:21:10.3441707 Information Initializing Reload (0), Initializing (21609500), Finished (21609610)<BR />10/15/2010 08:21:10.3441707 Error Task aborted.<BR />10/15/2010 08:21:10.3597957 Error The task "Qlikview_Dev/Research/test_sc/buildQVD.qvw" failed. ErrorCount=3<BR />10/15/2010 08:21:10.3597957 Information Sending Alert Mail to 1 recipients.<BR />10/15/2010 08:21:10.4222957 Information Finished (0)</P><P>Database Error message</P><P>CONNECTION_ERROR: ERROR: File OdccSocket.cpp line 105: Error in send: Connection reset by peer<BR />20101015122126 INFO: MemoryUsage Thread 1090525536 TotalAllocated 5676786289 TotalUnreleased 2433 Peak 75095786<BR />20101015122126 CONNECTION_ERROR: ERROR: File OdccSocket.cpp line 105: Error in send: Broken pipe<BR />20101015122126 INFO: ConnectionEnd Thread 1132489056<BR />20101015122126 INFO: MemoryUsage Thread 1132489056 TotalAllocated 77907338 TotalUnreleased 144 Peak 7527654<BR />20101015122129 INFO: ConnectionStart Thread 1132489056 User appuser Host 10.20.13.10<BR />20101015122129 INFO: GraphQueries Thread 1132489056 NumRequests 1</P><P></P><BR /><BR /></BODY></HTML> Mon, 26 Jan 2026 18:19:17 GMT https://community.qlik.com/t5/QlikView/ODBC-timeout/m-p/157397#M1309776 2026-01-26T18:19:17Z ODBC timeout https://community.qlik.com/t5/QlikView/ODBC-timeout/m-p/157398#M1309778 <HTML><HEAD></HEAD><BODY><P>Few things:</P><P></P><UL><LI>depending on database load, parameter value... some queries might take much longer than 7 minutes</LI><LI>some parameter values might result in invalid SQL . Log the "loop counter" and manually run the query with the last logged value</LI><LI>If you really issue a query every 7 minutes, there cannot be an "idle timeout". But there can be a "total duration timeout", which you can test for . Temporarily put the CONNECT statement inside the loop.</LI></UL><P></P><P>-Alex</P><P></P></BODY></HTML> Mon, 18 Oct 2010 09:48:15 GMT https://community.qlik.com/t5/QlikView/ODBC-timeout/m-p/157398#M1309778 2010-10-18T09:48:15Z