hi roger, thank you for the fast answer...
but the problem is whlie the query with the long duration is running the auto reload time will be increased. and after the long query is executed the auto reload is still about 600 seconds. that means the next keep alive query is sent after 10minutes which is definitly to late to keep the session alive.
while the long query is running, it is not necessary to execute the keep alive query because while the long query is executed the connections is still alive. but after the long query it is necessary that the keep alive query is executed every minute, so that the connection always stay alive.
so is it possible to reset the auto reload time to 1 minute after the query with the long duration is completed?
im sorry about my explaination, i hope its no to hard to understand :-) as you see, im no an english geek!
but thank you for the patience and help..
first of all we use DbVisualizer 5.0 Personal on Windows XP.
we have a problem with the auto reload function in DB Visualizer. we use the Monitor window to every minute auto execute one query to keep the connection to the DB2 System alive. that all works perfectly but if we execute a query manually that takes longer than 1 minute the auto reload function increase the auto reload time. this is normal and described in the following user manual entry:
Note: The specified number of seconds may be increased automatically by DbVisualizer if the total execution time for all monitors is longer than the specified value.
but the problem is, our DB2 system accepts only a timeout of max. 3 minutes. that means if the autoreload time is increased to more than 3 minutes DbVisualizer gets disconnected from the DB2 system after this 3 minute timeout. and thats no the sense of our keep alive query.
now my question, is it possible wo turn this auto increase function off?
Thank you in advance..