DEADLOCK OR TIMEOUT? 1

[IFTHENELSE]

I am having a heck of a time trying to figure this out.I have a single application accessing a single DB2 UBD(v6.1) database.I continue to get this error returned to my application:

[IBM][CLI Driver][DB2/NT] SQL0911N The current transaction has been rolled back because of a deadlock or timeout. Reason code "68". SQLSTATE=40001

I have created monitors that show no deadlocks or lock escalations.So my guess has been my application is timingout.I have increased my Lock Time Out but still get this error.My monitor shows that I have 2,459,372.6971(ms)wait on locks this is by no means efficent.Another intresting point when I do increase the Lock Time Out this error doesn't occur until the Time Out his hit and then it continues to the next record set.This happens at every increase of the Lock Time Out.I have it currently set at 600seconds(10min).If anyone can please give me any assistance I would be greatly appreciative.

 

[alphonsus]

Hello,

maybe this can help:

while your application is hanging, issue the command at the OS prompt (open another session) &quot;db2 get snapshot for locks on <YourDb>&quot; and look for an Application with Lock-wait status. If you're using the correct monitor it should say who is holding the lock and what kind of locks they are.

Hope it helps,

Alphonsus.

 

[IFTHENELSE]

Thank you fro the suggestion.I have been reading about snapshots just wasnt sure how to get it done.I will give this a try and post the results for you to see.thanks againg.