By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
449,277 Members | 1,237 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 449,277 IT Pros & Developers. It's quick & easy.

DB2 deadlock while accessing plan?

P: n/a

Folks,

I have been getting SQLCODE -911 while reading data from a table.
When I look at the db2diag.log file I see following:

2006-10-10-14.33.13.384726-240 I127058C470 LEVEL: Warning
PID : 233904 TID : 1 PROC : db2agent (CFG) 0
INSTANCE: db2prod NODE : 000 DB : CFG
APPHDL : 0-1415 APPID: *LOCAL.db2prod.061010183323
FUNCTION: DB2 UDB, access plan manager, sqlra_find_pkg, probe:99
RETCODE : ZRC=0x80100002=-2146435070=SQLP_LDED "Dead lock detected"
DIA8002C A deadlock has occurred, recovering transaction "".
Under what circumstance would DB2 run into deadlock situation while accessing
a plan?

I checked the timestamp of the compiled code and package, they were both
changed last week (Oct 4). I am running DB2 UDB 8.2 on AIX 5.3.

No other application was accessing this table when I got deadlock. My
application is written in C and uses static SQL, the package was bound with
ISOLATION UR.
--
Hemant Shah /"\ ASCII ribbon campaign
E-mail: No************@xnet.com \ / ---------------------
X against HTML mail
TO REPLY, REMOVE NoJunkMail / \ and postings
FROM MY E-MAIL ADDRESS.
-----------------[DO NOT SEND UNSOLICITED BULK E-MAIL]------------------
I haven't lost my mind, Above opinions are mine only.
it's backed up on tape somewhere. Others can have their own.
Oct 10 '06 #1
Share this question for a faster answer!
Share on Google+

This discussion thread is closed

Replies have been disabled for this discussion.