We were recently testing an application against V5R2. A couple of external SQL queries -- running via Client Access ODBC, which had been OK -- suddenly started failing with error SQL0666 (SQL Timeout). I understand the reason for this is that the optimizer thinks it's going to take longer to execute the query than its default timeout period. I'm wondering if there was a change between OS/400 at V5R1 and V5R2 that triggered this?
In V5R2 a new SQL Query Engine (SQE) was delivered that includes new algorithms and methods for the query optimizer to use. To learn more about SQE, click here.
MORE INFORMATION ON THIS TOPIC
Search400.com's targeted search engine: Get relevant information on DB2/400.
The Best Web Links: tips, tutorials and more.
Check out this Search400.com Featured Topic: Database issues resolved
Dig Deeper on DB2 UDB (universal databases)
Related Q&A from Kent Milligan
When working with DB2 files with columns that have both short and long names, there is no option choose which column names are returned via ODBC ... Continue Reading
When developing tables in a parent-child relationship, use a primary key and a foreign key along with a unique ID to make your database easier to ... Continue Reading
IBM did not change the default of the reuse deleted files function to YES for physical files in order to minimize the impact on any existing ... Continue Reading
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.