Locks – Timeout vs. Deadlock

You may also like...

7 Responses

  1. Scott says:

    Thanks a million for this website. We started WebSphere Commerce about a month ago and have not been to training, so this will be an invaluable website for me.

  2. Drazen says:

    hi.
    excellent article.
    Can you tell me how can I read deadlock deatails grom past for db2 9.5 ?
    Thanks,
    Drazen

    • Ember Crooks says:

      So I’m actually going to play with that, and will write a post on it.The detailed deadlock event monitor has only been deprecated in 9.7, so my normal build statement to create it still works, but I need to better understand what DB2 is replacing it with. I usually use a statement like this to create a detailed deadlock event monitor with more space, and I’ve used this on db2 9.7, so I know it still works:

      db2 “create event monitor my_detaildeadlock for deadlocks with details write to file ‘my_detaildeadlock’ maxfiles 2000 maxfilesize 10000 blocked append autostart”

      You’ll have to create the my_detaildeadlock directory in the db2event directory of the database path, and you have to create it before you see the deadlocks. After that, it’s a simple matter of the normal event monitor flushing and then parsing using db2evmon.

    • Ember Crooks says:

      So check out this post: http://db2commerce.com/2012/01/18/analyzing-deadocks-the-old-way/
      You can still use this method in 9.5 and 9.7. I’m still investigating the new methods.

  1. January 4, 2012

    […] Deadlocks are not a database problem. The symptoms sure show up on the database, but they are symptoms of an application problem. For more information on deadlocks, see Deadlocks vs. Locktimeout. […]

  2. January 18, 2012

    […] by Ember Crooks on January 18, 2012 Digg DiggIn 9.7, DB2 changed the default monitoring methods for deadlocking. If you’re at all confused about the difference between deadlocks and lock timeouts, please first read my post on Deadlocks VS. Lock timeouts. […]

Leave a Reply

Your email address will not be published. Required fields are marked *