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

getting a (-911)deadlock error while dropping a procedure

P: n/a
Hi,

I am getting a error sqlcode : -911, sqlstate : 40001 error, i.e.
Deadlock error while trying to drop the procedure.
I had seen cases of getting deadlocks in a table but not in
procedures.

Nobody is doing a call on that procedure.
What could be the reason for it.

More importantly, what will be the fix.

Thanks

Rahul
Dec 6 '07 #1
Share this Question
Share on Google+
1 Reply


P: n/a
On Dec 6, 5:02 am, Rahul Babbar <rahul.babb...@gmail.comwrote:
Hi,

I am getting a error sqlcode : -911, sqlstate : 40001 error, i.e.
Deadlock error while trying to drop the procedure.
I had seen cases of getting deadlocks in a table but not in
procedures.
911 has a reason code: it is either 2 - deadlock or 68 - lock timeout.
I would guess (actually I'd bet money) that you are getting a 68, a
lock timeout. I often get these when I am working on something: I have
the DROP/CREATE in one window and the CALL in the other, and if I
forget to COMMIT, well...

That -911 code and message is one thing I think IBM should change. I'd
like to see a different message, something like 'your transaction has
been rolled back due to a lock timeout' for a 68 instead of one
message with RC 2 or 68. I get reports of deadlocks even from
developers who should know better.
Dec 6 '07 #2

This discussion thread is closed

Replies have been disabled for this discussion.