Results 1 to 4 of 4
  1. #1
    Join Date
    Jan 2005

    Unanswered: Deadlocks across partitions?


    I have some jobs running 4 wide that open a cursor and then fetch rows from a single DB2 table. This table is partitioned by account number. Somehow, every so often, two of the jobs will collide with -911 deadlock errors, killing one of the jobs, even though they are accessing accounts in distinct partitions.

    Has anyone heard of -911 deadlock errors when the data being accessed is in separate partitions?

    The cursor does use account number in the WHERE clause.

    Please excuse the general nature of this note; any insight is appreciated.

  2. #2
    Join Date
    Nov 2004
    Hello! I am sorry for my poor English!

    Details are necessary (OS, version of DB2, isolation level, sample code and etc.)!
    Last edited by kdima71; 01-04-05 at 10:32.

  3. #3
    Join Date
    May 2003
    Make sure you check the reason code. RC 2 is deadlock, and RC 68 is lock timeout. They are not the same thing.

    If you are only doing selects, you cannot get lock contention since multiple share locks can coexist with eachother without any interference.

    Check to see if you are getting lock escalation (db2diag.log) and it might be a good idea to run a snapshot for locks.
    M. A. Feldman
    IBM Certified DBA on DB2 for Linux, UNIX, and Windows
    IBM Certified DBA on DB2 for z/OS and OS/390

  4. #4
    Join Date
    Sep 2004
    If those jobs are just reading and not updating the table, make sure that they access the table with the correct isolation level; if necessary, set the isolation level to CS (cursor stability) or even to UR (uncommitted read).

    -- Peter.

Posting Permissions

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