Friends

Is there any way other than force application.

Here is the scenario where Iam stuck:

I was executing 8 table join complicated query. After an hour I did control C but query does not get killed and the session hangs.

Immediately I tried "db2 force application (ID)"
DB2 says sucessful but still that process is found in "db2 list applications"

Again I tried couple of times "db2 force application (ID)" ..
Does not help.

Did any one know how to kill that process with out bringing down the DB.

Note: This is 24*7 Production DB
Diffrent users running few complicated queries.
Load processes are busy.

Thanks for youre help
Racha

force application all
also doesn't work?????!!!!!

"Force Application all" will terminate all other application processes.

But, I told in the last notes. I need to force my application only.


Thanks
Racha

can u kill the db2agent ??

Hi,

The force application command is an Asynchronous Command so it may not come immediately into effect. That's the reason why you see the application still active even after forcing it off.

My observation is that this command works, however being asynchronous in nature it does not come into effect immediately.

Regards

Nitin.

Yes thanks Nitin

Its true

Force application does not take effect immediately.
It took me 9 hours to force it

Horray DB2 Team!!!
Racha

Try these two commands

ipclean or ipclean -a

these might help. My guess is that a few db2 processes became zombie processes in your server and were hanging.

what can this command do??

From my own experience:
On the force of an application or the direct killing of the connected application the database must rollback uncommitted operations. If there's a large amount of work involved that rollback can take quite a bit of time. The application will still show until the rollback is complete. You can confirm with list applications show status - status of the force app will be rolling back.

Applications which are in lock wait status at the time of a force will not clear until they are able to rollback. The rollback is not possible until the lock contention has cleared. List apps will continue to show lock-wait until the lock contention clears and then the app will rollback any uncomitted work.

Check the page http://www.db2click.com/scripts.htm for a sample script

Sathyaram

Referring to
can u kill the db2agent ??

Do not do this - it will bring the instance down.

Were you trying to save the results of the query to a table? I have found that if there are several concurrent transactions a forced application can take a long time to disconnect since db2 is trying to write to as well as rollback through logs. If the logs are archived directly to tape then it has to get the logs from the tape system as well. Just my observation.