Results 1 to 4 of 4

Thread: db2 deadlock.

  1. #1
    Join Date
    Oct 2012
    Posts
    4

    Unanswered: db2 deadlock.

    Hi, I am using DB2 9 version and WAS7. We have a table which is not used for long time. When I was doing the development, I was able to work on it and complete the dev work. But when the app when to testing, i am seeing the locks on this table.

    [11/8/12 15:01:21:861 CST] 00000010 FfdcProvider W com.ibm.ws.ffdc.impl.FfdcProvider logIncident FFDC1003I: FFDC Incident emitted on C:\Program Files (x86)\IBM\SDP\runtimes\base_v7\profiles\was70profi le2\logs\ffdc\BLS_AP_48464846_12.11.08_15.01.21.73 67942210057037768674.txt com.ibm.ws.rsadapter.jdbc.WSJdbcResultSet.next 2624
    [11/8/12 15:01:21:876 CST] 00000010 worklist E com.agencyport.paging.worklist.WorkListProviderImp l getResults Standard SQL Exception Info for exception at level 0 - SQL State: '40001'; SQL Error Number: '-911'; SQL Error Text: 'The current transaction has been rolled back because of a deadlock or timeout. Reason code "68".. SQLCODE=-911, SQLSTATE=40001, DRIVER=3.63.75';
    [11/8/12 15:01:21:907 CST] 00000010 worklist E com.agencyport.paging.worklist.WorkListProviderImp l getResults com.ibm.db2.jcc.am.SqlTransactionRollbackException : The current transaction has been rolled back because of a deadlock or timeout. Reason code "68".. SQLCODE=-911, SQLSTATE=40001, DRIVER=3.63.75

    Above is the error log, can you please let me know how to resolve this.
    Thanks,
    Kumar.

  2. #2
    Join Date
    Oct 2009
    Location
    221B Baker St.
    Posts
    486
    Determine what has caused the lock(s) and correct the problem(s). This is most likely a transaction flow design problem.

  3. #3
    Join Date
    Oct 2012
    Posts
    4
    I think it is table which is causing this problem. I tried to change the code instead of MERGE sql query to insert or update when required. It is still an issue.

  4. #4
    Join Date
    Oct 2009
    Location
    221B Baker St.
    Posts
    486
    It is Most Probably Not the table which is causing this problem.

    If something is locked, changing what you changed will not resolve the problem.

    You need to determine when locks are acquired, in which order (done incorrectly can cause what is known as a fatal embrace), and how long the locks are in effect.

    The design of the code (when there are multiple concurrent transactons) is your problem. Indivudually run, i suspect these errors do not happen.

Posting Permissions

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