ODBC Error Messages: Determining if your query needs to be refined
Symptoms
- query timed out while processing
- driver times out waiting for a response
Cause
If you receive an error message that your query did not return in the expected amount of time, it is likely that the query was too general and timed out while processing.
Resolution
If you receive the following error message when running an ODBC query,
Refine your query by adding more filter conditions. Avoid multi-table joined aggregate queries whenever possible. Instead, issue a query against a pre-defined database view.
If you receive the following error message when running an ODBC query,
[DataDirect][ODBC OpenAccess SDK driver][OpenAccess SDK SQL Engine]
Error Message: Method failed: (https://myinstance.service-now.com/mytable.do?SOAP&displayvalue=all) HTTP/1.1 502 Bad Gateway with code: 502
Your query did not return in the expected amount of time. Please limit your query and try again., the query you have issued timed out while processing. Normally, the Apache web server serving your instance's web service has a default timeout set at 5 minutes. When a request requires more than 5 minutes to process, the error message appears.Refine your query by adding more filter conditions. Avoid multi-table joined aggregate queries whenever possible. Instead, issue a query against a pre-defined database view.