Re: transaction lock (TX) on table block with PK

From: Matthias Hoys <anti_at_spam.com>
Date: Wed, 15 Mar 2006 19:44:50 +0100
Message-ID: <441860a5$0$22352$ba620e4c@news.skynet.be>

"NetComrade" <netcomradeNSPAM_at_bookexchange.net> wrote in message news:55lg121k02llci21tvlmqsjt7bg0m40ub4_at_4ax.com...
> In what case is this possible?
> the update statements I saw were something like;
>
> update my_table set other_column=other_column+1 where id=:my_id;
> other_column is not being referenced..
> I cannot really reproduce it via sqlplus, but as soon as I have 2
> sessions issuing the statement above on 2 different PK's, I see
> enqueue waits on other sessions creeping up... They're all waiting for
> the same block. The block is probably some table header block.
>

Do you have un-indexed foreign key columns pointing to this PK ? Received on Wed Mar 15 2006 - 12:44:50 CST