Win a copy of Zero to AI - A non-technical, hype-free guide to prospering in the AI era this week in the Artificial Intelligence and Machine Learning forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Liutauras Vilda
  • Paul Clapham
  • Bear Bibeault
  • Jeanne Boyarsky
Sheriffs:
  • Ron McLeod
  • Tim Cooke
  • Devaka Cooray
Saloon Keepers:
  • Tim Moores
  • Tim Holloway
  • Jj Roberts
  • Stephan van Hulst
  • Carey Brown
Bartenders:
  • salvin francis
  • Scott Selikoff
  • fred rosenberger

WebSphere DB2 Deadlock Exception. Reason code "2"

 
Greenhorn
Posts: 19
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I'm using IBM WebSphere Application Server Advanced Edition 4.0.1 and IBM UDB 7.0. Offlate i'm getting a continuous deadlock error in most of the system transactions. Pls provide with some inputs as its affecting many production users.

COM.ibm.db2.jdbc.DB2Exception: [IBM][CLI Driver][DB2/6000] SQL0911N The current transaction has been rolled back because of a deadlock or timeout. Reason code "2". SQLSTATE=40001

Its not happening on a specific application, but on sparingly on all application for last 1 month. Is there a patch or fix from DB2 or WebSphere which solves this? I'm sure its not a generic error accross all users of this combination (WAS + IBM DB2 UDB). Any inputs and feedback is appreciated.

Note: The WebSphere App Server is configured to connect to DB2 using datasource.
 
Greenhorn
Posts: 1
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Main reason for this error will be deadlock time out properties. To view this property value issue the following command:

Display Database Manager Configuration Settings:


Display Database level Configuration Settings



If dead lock time out value is -1 then change to either 60 or 120 sec based on your DB transaction.



n - number of sec.

For more information on dead lock please visit this link

http://db2forum.blogspot.com/2011/10/db2-lock.html
 
reply
    Bookmark Topic Watch Topic
  • New Topic