IBM seems to think we should just accept that the process now takes longer with the following statement: "As far it doing a good job, all the files are using logicals and from the statistic information there, the join order looks good. This means there is no obvious way to make it run faster. I must admit I am puzzled to how this ever ran faster. However, if you are hitting some of the problems with Select/Omit logicals, SI17357 will clean those up."
We are positioning ourselves to test the PTF but have not as of this writing. Was there something in the February group PTF that could cause a report to take 40-50 minutes longer.
I'd strongly suggest you continue to work with IBM Support to test out your queries with the latest PTFs.
MORE INFORMATION ON THIS TOPIC
Visit the ITKnowledge Exchange and get answers to your DB2 questions fast.
Check out this Search400.com Featured Topic: Expert advice on DB2
Search400.com's targeted search engine: Get relevant information on DB2/400.
Dig Deeper on DB2 UDB (universal databases)
Related Q&A from Kent Milligan
To solve the SQL error -321 on IBM i6.1, use the new values statement to overcome the error. If you are using an older release, declare a cursor ... Continue Reading
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
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.