Re: seen a Select (just a select no select for update) take out a Table Exclusive lock (TX)
- From: Edgar Chupit <chupit@xxxxxxxxx>
- To: lawrence.wolfson@xxxxxxxxxx
- Date: Fri, 27 Jan 2006 13:30:16 +0200
Larry,
Besides the causes that already have been mentioned, transaction lock
(TX) can be caused by transaction control statement "set transaction".
Maybe application that had query and caused TX lock, before query
executed set transaction name 'xxx' or something like this.
On 1/26/06, Wolfson Larry - lwolfs <lawrence.wolfson@xxxxxxxxxx> wrote:
> From one of the other DBAs here:
>
> "Have any of you ever seen a Select (just a select no select for update)
> take out a Table Exclusive lock (TX) ? we had one in SAP this morning on
> ZPICK01 and the developers assure me that the transaction doesn't try to
> update the table. The only thing I can think of, is that ZPICK01 is huge
> and that Oracle tried to ensure some form of Read Consistency by making
> the table TX. That said I'm still not certain that some switch in the
> transaction isn't set to lock the table. Thoughts ?"
>
>
> Thanks
> Larry
--
Best regards,
Edgar Chupit
callto://edgar.chupit
--
//www.freelists.org/webpage/oracle-l
Other related posts:
