Discussion:
Idle Connections holding any open Log ?
(too old to reply)
Shashi Shekhar
2016-07-06 13:18:43 UTC
Permalink
Hello everyone,

I am working on DB2 DBA on AIX.
We see many connections to DB2 get's idle ( over 2 hours) and which doesn't get closed automatically. We have to force them manually with "force application" command.

But how we can make sure that the idle connections doesn't have any open log?

Thanks in advance.


Regards
Shashi
AngocA
2016-07-07 01:10:56 UTC
Permalink
Do you have a connection pool in the application server that connects to the database? if that is the case, then having idle connections are normal.

You have to find the oldest transaction to see if the connection have open transactions. Also, you should analyze those transaction before kill them, what is the last operation they do? what locks do they have?
Luiz da Silva
2016-07-07 08:26:58 UTC
Permalink
Post by Shashi Shekhar
Hello everyone,
I am working on DB2 DBA on AIX.
We see many connections to DB2 get's idle ( over 2 hours) and which doesn't get closed automatically. We have to force them manually with "force application" command.
But how we can make sure that the idle connections doesn't have any open log?
Thanks in advance.
Regards
Shashi
The problem is not having a idle, but holding a not-committed transaction for a long time.

This might be interesting for you: http://db2commerce.com/2016/02/02/preventing-log-saturation/
Continue reading on narkive:
Loading...