Results 1 to 11 of 11
  1. #1
    Join Date
    Oct 2003
    Posts
    29

    Thumbs down Unanswered: Force Application Does not force

    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

  2. #2
    Join Date
    Nov 2003
    Posts
    14
    force application all
    also doesn't work?????!!!!!

  3. #3
    Join Date
    Oct 2003
    Posts
    29
    "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

  4. #4
    Join Date
    Nov 2003
    Posts
    14
    can u kill the db2agent ??

  5. #5
    Join Date
    Jul 2003
    Location
    Austin, TX, USA
    Posts
    278

    Force Application

    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.

  6. #6
    Join Date
    Oct 2003
    Posts
    29
    Yes thanks Nitin

    Its true

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

    Horray DB2 Team!!!
    Racha

  7. #7
    Join Date
    May 2003
    Posts
    369

    other ways

    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.

  8. #8
    Join Date
    Nov 2003
    Posts
    14
    what can this command do??

  9. #9
    Join Date
    Aug 2002
    Location
    St. Louis
    Posts
    16
    Originally posted by udb_dba
    Yes thanks Nitin

    Its true

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

    Horray DB2 Team!!!
    Racha
    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.

  10. #10
    Join Date
    Aug 2001
    Location
    UK
    Posts
    4,650
    Check the page http://www.db2click.com/scripts.htm for a sample script

    Sathyaram
    Visit the new-look IDUG Website , register to gain access to the excellent content.

  11. #11
    Join Date
    Mar 2003
    Posts
    343
    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.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •