View previous topic :: View next topic
|
Author |
Message |
rohanatl
New User
Joined: 21 Oct 2005 Posts: 22
|
|
|
|
HI All,
One of our CICS transcaction has failed with dead lock, On analysis we could see that one of the batch program which run every 5 mins is causing the transcation to end in Deadlock
Both the transcaction and batch is using the same db2table to update.
Code: |
THREAD-INFO=XXXX:*:*:*
IS DEADLOCKED WITH PLAN=PPPPPXXX WITH
CORRELATION-ID=PPPPPPPP
CONNECTION-ID=BATCH |
Please suggest how we can avoid this deadlock.
Thanks |
|
Back to top |
|
|
dbzTHEdinosauer
Global Moderator
Joined: 20 Oct 2006 Posts: 6966 Location: porcelain throne
|
|
|
|
how about explaining what the batch job does.
and explain what the transaction does. |
|
Back to top |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006 Posts: 19244 Location: Inside the Matrix
|
|
|
|
Hello,
Is this resolved?
The problem is a design issue. One of the processes locks resource A and then tries to lock resource B. At the same time, another process locks resource B and then tries to lock resource A. It may not be trivial to change/correct, but the transactions should lock resources in the same order. |
|
Back to top |
|
|
|