Re: deadlock
From: Gints Plivna <gints.plivna_at_gmail.com>
Date: Wed, 27 Mar 2013 22:36:21 +0200
Message-ID: <CAN2wOq0De3K0KD_uz35fbiZ-fYhhobTA9kxX8zY0zRtsPjqJsg_at_mail.gmail.com>
Question is WHY? Why someone would need to lock the table to select the rows?
Couldn't find that info.
BTW if it is something like trying to simulate queue, then one option would be to use AQ, or manually use "select for update skip locked" clause (documented in 11g, undocumented in a few previous versions).
Date: Wed, 27 Mar 2013 22:36:21 +0200
Message-ID: <CAN2wOq0De3K0KD_uz35fbiZ-fYhhobTA9kxX8zY0zRtsPjqJsg_at_mail.gmail.com>
Question is WHY? Why someone would need to lock the table to select the rows?
Couldn't find that info.
BTW if it is something like trying to simulate queue, then one option would be to use AQ, or manually use "select for update skip locked" clause (documented in 11g, undocumented in a few previous versions).
Gints
2013/3/27 Barbara Baker <barb.baker_at_gmail.com>
> 10.2.0.1.1 database on windows. Response is slow. Application seems to be
> a piece of crap.
> I set trace on for his session, and he re-enacted the "slowness"
> Details of the deadlock are below. After I traced the session and
> explained to the developer that his code created a deadlock when it should
> not have, here's what I got back from him:
> Barb,****
>
> ** **
>
-- http://www.freelists.org/webpage/oracle-lReceived on Wed Mar 27 2013 - 21:36:21 CET