How to rid of Deadlock or timeout?

[cristi22]

Hi,
Please help with the deadlock...
I already did "force application all"....did not work and set the integrety does not work coz of the deadlock...

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

Lock Name = 0x00060265000000000000000054
Lock Attributes = 0x00000000
Release Flags = 0x40000000
Lock Count = 1
Hold Count = 0
Lock Object Name = 613
Object Type = Table
Tablespace Name = USERSPACE1
Table Schema = ASYS
Table Name = MEMBER_WORK_PERIOD_FUND_BK
Mode = Z

thanks!
c

 

[MarcLodge]

Hi Cristi,

Reason code 68 signifies a time out rather than a deadlock, so it is this that needs investigating. You need to look in the DB2 log for whatever platform you are on, and there should be messages in there to indicate what is attempting to acquire the table, and what is holding it. Obviously your tran is attempting to acquire, but you will need to look at the other tran, whatever that may be, and find out why it is holding the lock for such a long time. This might be an error, a piece of rogue code, or even possibly an intentional design to stop updating or accessing the data whilst maintenance is taking place.

You first place to look is the DB2 log.

Hope this helps.

Marc