Re: select only user causing locks?
- From: jungwolf <spatenau@xxxxxxxxx>
- To: JayMiller@xxxxxxxxxxxxxxxx, Oracle-L <Oracle-l@xxxxxxxxxxxxx>
- Date: Tue, 10 May 2005 12:22:47 -0500
Thanks for the response, Jay. This is probably a "chicken little"
issue compared to all the other things we need to deal with.
On 5/10/05, JayMiller@xxxxxxxxxxxxxxxx <JayMiller@xxxxxxxxxxxxxxxx> wrote:
> Is it possible to have a session trigger on a lock table or select for
> update statement? If so you could set it to email you should the situati=
on
> recur.
I'm not seeing any type of trigger for "on lock" or "on select", at
least not in 9i. "Set transaction read only" stops "select for
update" but not "lock table", and of course has its own problems.
This doesn't seem to be solvable at the database level.
Every shop I've walked into had a readonly account if for no other
reason than to let someone in a business department investigate data
error issues. Here they have Toad or Sqlplus and no prospect of
getting a different tool. Has anyone else been bit by the "select for
update" behavior of Toad?
Oracle has lots of gotchas. This one surprised me because it can
completely lock an application.
Steven
--
//www.freelists.org/webpage/oracle-l
Other related posts:
