Oracle EE 9.2.0.6 without extra cost options is being used for housing
production OLTP data. In-house developers occasionally use TOAD 8,
SqlPlus 9.2.0.6, etc. to query the production data while debugging
end-user complaints. One third-party tool issued a SELECT FOR UPDATE
when a developer intended only to SELECT the row. This developer did
not have any update privileges, but the database created the row lock
just the same, blocking legitimate updates while the lock is held by
this read-only developer. This blocking ability can delay a millisecond
response for normal updates.
The developers will modify their usage for the offending tool. But, is
there a recommended workaround that the DBA could implement at the
database level to prevent SELECT FOR UPDATE by read-only end-users?
Received on Sun May 01 2005 - 09:09:50 CDT
