How can I reinstate the first run condition for a query without IPLing my system? I'm at V5R2. I did try the CLRPOOL command and SETOBJACC, but didn't have any luck.
Any query interface on the iSeries (SQL, Query/400, OPNQRYF, etc) would have the same behavior of running faster on the second time if objects stay resident in memory.
Not sure why you don't think that SETOBJACC isn't working to clear objects, but that would be the preferred method over the CLRPOOL command. With SETOBJACC, you also need to remember to clear out any indexes or keyed logical files used by the query optimizer in the implementation of your query.
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.