[mvo@work]

Hi,

We're running UDB 7.1 (yes, upgrade is on its way) on Solaris. I have a number of users using DB2 command center to connect to the database and they often don't terminate their session at the end of the day after issuing a SELECT that can return a large result set. Therefore, the locks are never released and the online application sometimes fails to insert into the database because the transaction log is full.

Is there any config parameter that will cause DB2 to terminate those threads when they go inactive for a given time period ?

Thanks

[n_i]

I think you can use DB2 Governor utility to disconnect idle and/or long-running applications.