Analyzing Deadocks – the old way

You may also like...

8 Responses

  1. Ray Houle says:

    Ember,

    Wounderful post ! I greatly appreciated the end to end “how to” approach, good cross-references.

    Thanks

  2. imran says:

    Its a good article explained here for DBA’s to get through deadlock issues.

  3. Lee Goddard says:

    What a great blog on locking. I learned a lot about the new get_mon functions. Ember is my new hero for the week! U ROCK Ember!

    Lee

  4. Andres Gomez says:

    Line ‘db2 “set event monitor ros_detaildeadlock state=1″‘ is incorrect, the event monitor name, it should be ‘db2 “set event monitor my_detaildeadlock state=1″‘

  1. February 13, 2012

    […] and if you want to avoid event monitors that write to tables, that’s still the only way. See Analyzing Deadlocks – the old way for more details on that […]

  2. March 2, 2012

    […] Analyzing Deadocks – the old way Gives a detailed look at deadlock analysis before 9.7 – a method that still works in 9.7. This was mentioned in the DB2′s Got Talent presentation, but was not covered in detail […]

  3. March 9, 2012

    […] Analyzing Deadocks – the old way […]

Leave a Reply

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