seen a Select (just a select no select for update) take out a Table Exclusive lock (TX)

From: Wolfson Larry - lwolfs <lawrence.wolfson_at_acxiom.com>
Date: Thu, 26 Jan 2006 15:22:44 -0600
Message-ID: <B39B7B7D8C8CEA419D0ED45FD7FA4C53FB37E5@CWYMSX06.Corp.Acxiom.net>

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 ?"

Gee, I haven't worked much on SAP lately, but I believe tables prefixed Y and Z are custom tables, although I don't see why that would make a difference.

	Thanks
	Larry

 
 


*************************************************************************

The information contained in this communication is confidential, is intended only for the use of the recipient named above, and may be legally privileged.

If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited.

If you have received this communication in error, please resend this communication to the sender and delete the original message or any copy of it from your computer system.

Thank you.

---

--
http://www.freelists.org/webpage/oracle-l

Received on Thu Jan 26 2006 - 15:22:44 CST