I think it's doing rollback, I would not do anything because even if you
stop it, when you restart it has to go through crash recovery and
rollback.

It's very normal depends on how long your transaction has been running.

Regards,
Kondal R YENNARAM
The Home Depot


-----Original Message-----
From: divakar
[mailto:db2udbdba-ezmlmshield-x817762.[Email address protected]
Sent: Monday, August 29, 2005 10:14 AM
To: LazyDBA Discussion
Subject: db2stop force



Our DB2 transaction Log File was full. We tried to kill the application
that was responsible for it. But even after using DB2 force applications
all' several times the application was still running. Lastly we tried
'd2stop force'. It has been more than 1.5 hours but the command('d2stop
force') is still executing. Is it normal?


While it is still running NO errors has been reported in db2diag.log.


Our Log File size is almost 20GB.

Environment DB2 8.2 / AIX.


Divakar




Confidentiality Notice


The information contained in this electronic message and any attachments
to this message are intended for the exclusive use of the addressee(s)
and may contain confidential or privileged information. If you are not
the intended recipient, please notify the sender at Wipro or [Email
address protected] immediately and destroy all copies of this message
and any attachments.


---------------------------------------------------------------------
PLEASE CLICK REPLY-ALL TO SEND A REPLY TO EVERYONE
website: http://www.LazyDBA.com
To unsubscribe: http://www.lazydba.com/unsubscribe.html


DB2 & UDB email list listserv db2-l LazyDBA home page