try db2_kill

then increase the size of the file system for the log and or increase # of
logs if needed and start again.

You may have to remove the queues , semaphores and shared memory owned by
that instance via ipcrm.
There will be one shared memory left that is ok.






"divakar"
<db2udbdba-ezmlms
hield-x817762.x11 To
[Email Address Removed] "LazyDBA Discussion"
com> <[Email address protected]
cc
08/29/2005 11:14
AM 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