Re: Problem with ODBC
Sheshnarayan Agrawal a prￜsentￜ l'ￜnoncￜ suivant : Hello! thanks for your answer! > Could you check your ODBC trace to ensure under the cover its not calling > SQLCancel API and/or make sure its not calling SQLSetStmtAttr with > SQL_ATTR_QUERY_TIMEOUT option? If its making calls to one of these APIs to > ODBC driver then its likely that your given query is taking more time than > desired and timing out with -213 error !! Where can I trace these options? > Could you also post exact error > information which you get from ODBC? it says error 3146 [informix][Informix ODBC Driver][Informix] statement interrupted by user (#-213) > Also could you post the version of CSDK? 2.90.TC6 > >>> When I open the table, there is no problem, it shows me all records (a > lot... more than 500'000 records). > Are you using SQL Linked Server? I hope you are not expecting 500K > records? No, result shoud be about 2000 records > Are you trying to create view using Query Analyser and then use > Enterprise Manager to open that view? And that takes long time (so many > rows than desired)? If so, and if you are not using CSDK 2.90.TC6 onwards > then you might want to switch to 2.90.TC6 onwards for better performance. > I am using Access, and this query should creat a table that I can use to make further treatement. It really takes a very long time, so a timeout could be possible. Another possibility I think about is if there are userlocks on some records. kind regards Beat
>>Where can I trace these options? Start->Control Panel -> Administrative Tool ->Data Source (ODBC)->Tracing Tab then supply absolute path name for the trace file (i.e c:\\my_dir\\trace.txt) under "Log File Path"after that click on "Start Tracing Now" (Don't forget to disable tracing once you are done), Run your application. Once your application is over search for SQLCancel and/or SQL_ATTR_QUERY_TIMEOUT in trace.txt file. -Shesh Beat Leuppi <ng@bl.endjunk.com> Sent by: informix-list-bounces@iiug.org 19/05/2008 18:19 Please respond to bloop@bl-c.ch To informix-list@iiug.org cc Subject Re: Problem with ODBC Sheshnarayan Agrawal a présenté l'énoncé suivant : Hello! thanks for your answer! > Could you check your ODBC trace to ensure under the cover its not calling > SQLCancel API and/or make sure its not calling SQLSetStmtAttr with > SQL_ATTR_QUERY_TIMEOUT option? If its making calls to one of these APIs to > ODBC driver then its likely that your given query is taking more time than > desired and timing out with -213 error !! Where can I trace these options? > Could you also post exact error > information which you get from ODBC? it says error 3146 [informix][Informix ODBC Driver][Informix] statement interrupted by user (#-213) > Also could you post the version of CSDK? 2.90.TC6 > >>> When I open the table, there is no problem, it shows me all records (a > lot... more than 500'000 records). > Are you using SQL Linked Server? I hope you are not expecting 500K > records? No, result shoud be about 2000 records > Are you trying to create view using Query Analyser and then use > Enterprise Manager to open that view? And that takes long time (so many > rows than desired)? If so, and if you are not using CSDK 2.90.TC6 onwards > then you might want to switch to 2.90.TC6 onwards for better performance. > I am using Access, and this query should creat a table that I can use to make further treatement. It really takes a very long time, so a timeout could be possible. Another possibility I think about is if there are userlocks on some records. kind regards Beat _______________________________________________ Informix-list mailing list Informix-list@iiug.org http://www.iiug.org/mailman/listinfo/informix-list
Sheshnarayan Agrawal avait ￜnoncￜ : Hello >>> Where can I trace these options? > Start->Control Panel -> Administrative Tool ->Data Source (ODBC)->Tracing > Tab then supply absolute path name for the trace file (i.e > c:\\my_dir\\trace.txt) under "Log File Path"after that click on "Start > Tracing Now" (Don't forget to disable tracing once you are done), Run your > application. Once your application is over search for SQLCancel and/or > SQL_ATTR_QUERY_TIMEOUT in trace.txt file. > Timeout was the right keyword! I really found SQL_ATTR_QUERY_TIMEOUT in the trace-file. Now I have eliminated all "order by" in the SQL. I also put the fields with criteria in the beginning of the statement. Like this I now get a result! Thanks a lot! Beat