DB2 Connect times out after 60 minutes...
Posted on 2004-03-24
I have a query and reporting tool installed on Solaris. We have some very long running queries. Going against Oracle, there seems to be no problem, leading me to believe that the reporting engine (except for potentially the data access libs) is working fine.
When we run any long running query against db2/390, if the join time is over 60 minutes, there is nothing returned ever and the query on the db2 side goes to an RUW waiting state.
On windows, the tool appears to work fine. If the query starts returning data in 50 minutes and this takes longer than 10 minutes, then we're fine. It's only if the client waits for more than 60 minutes for feedback from db2 that we have a problem.
JDBC on the same box apparently has the same problem, (seems to time out, leaves process on host hanging in RUW), but not completely sure.
Does anyone know of a particular idle timeout for the db2 middleware (perhaps particular to DB2/390, not UDB) that can be examined?
Any thing I should look for in db2trc?