Results 1 to 3 of 3

Thread: DB2 Exception

  1. #1
    Join Date
    Sep 2004
    Posts
    2

    Unanswered: DB2 Exception

    Hi,

    We are getting the following exception in Production environment but we are unable to reproduce it.
    --------------------

    The current transaction has been rolled back because of a deadlock or timeout. Reason code "2". SQLSTATE=40001

    ****Detail of this exception*****
    Message:
    [IBM][CLI Driver][DB2/6000] SQL0911N The current transaction has been rolled back because of a deadlock or timeout. Reason code "2". SQLSTATE=40001

    ---------------------

    The sql logs show :

    ADM5503E The escalation of "1" locks on table "UDBADM .TABLE_CUST" to lock intent "X" has failed. The SQLCODE is "-911".

    ----------------------

    The process is as below.

    1) We are inserting into TABLE_CUST table (1 row / transaction)
    2) Parellel processing in place. ( JMS )
    3) Only inserts to this table. No updates.
    4) The insert process is supposed to take no more than 1 sec.
    5) The database lockout / timeout is set as 60 secs.

    We are not understanding the reason for the failure as we are unable to reproduce this again.

    Any suggestions / questions are highly requested. Please respond.

    Thank you,

    Prasad

  2. #2
    Join Date
    Sep 2004
    Posts
    2

    Unhappy

    Can anyone help me?.. please..

    Thanks,

    Prasad

  3. #3
    Join Date
    Jul 2004
    Posts
    2

    LOCKLIST value too low


Posting Permissions

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