Hello All ,

The transaction log gets filled up by some unknown application. We
recieve the below message in the db2diag.log

There is no application ID being listed.

ADM1823E The active log is full and is held by application handle
"". Terminate this application by COMMIT, ROLLBACK or FORCE
APPLICATION.


We observered there are some indoubt transactions . Commiting /
Rolling back those transactions doesn't get the log usage back to
normal. We had to restart the instance every time.

Any workarounds for this issue without restarting the instance ??


Thanks,
Kamalnath.V

On Sep 16, 8:01*am, Gladiator <vkamalnath1... (AT) gmail (DOT) com> wrote:
db2 LIST INDOUBT TRANSACTIONS WITH PROMPTING

and then commit or rollback the indoubt transactions

Ricardo Marcos Alonso
http://www.blogdb2.com

On 2011-09-16 08:01, Gladiator wrote:
Not exactly the same problem as you are describing, but we had problems
with transactions that never where committed or rollbacked, i.e. spanned
a lot of logs. I've detected those via:

select
x.agent_id,
substr(z.corr_TOKEN,1,12) as ip,
cast(y.stmt_text as varchar(800)) as stmt,
x.locks_held,
x.APPL_IDLE_TIME,
x.UOW_START_TIME
from sysibmadm.SNAPAPPL x
join sysibmadm.snapstmt y
on x.agent_id = y.agent_id
join sysibmadm.SNAPAPPL_INFO z
on x.agent_id = z.agent_id
where UOW_STOP_TIME is null
and TIMESTAMPDIFF(8,CHAR(current_timestamp - UOW_START_TIME)) > 8
order by UOW_START_TIME;

and then forced the agent(s) holding the transaction. This was for LUW
9.5 a couple of fixpaks ago. I have not heard of the problem recently so
perhaps the problem is fixed in either the application or in one of the
more recent fixpaks.


/Lennart

On Sep 16, 8:01*am, Gladiator <vkamalnath1... (AT) gmail (DOT) com> wrote:
Sounds strange... how are your monitor settings (db2 get dbm cfg)?