Re: A row locking problem that baffles all...

It would appear that what you want can't be done. No-one here seems able to answer your question and Oracle can't. However, various sensible suggestions have been made as to how you can avoid the original problem occurring.

If it is such a big problem that it needs solving then I think you'll have to make changes to the application. If it ain't then why not just accept people's suggestions with grace? - or are you just out to show that you've got a problem which no-one can solve? If so I guess you've probably got more of a problem than you think....

Rick:-)

Paul S wrote:
>
> The original question was to establish who caused the block to the
> nowait lock. The scenario was a worst case situation.
>
> Our system is well established, successfully processing a massive
> amount of sensitive data, and so uses pessimistic locking so this
> sensitive data isn't compromised. Pessimistic locking has the
> shortfall that you mention (someone might leave a transaction with a
> lock open), but some of the biggest RDBs in the world use Pessimistic
> locking. 99.999% of all users commit / rollback their work as soon as
> they finish, and the others which hold locks for longer rarely cause
> problems as Oracle always has facilities to close sessions/kill
> sessions/warn sessions that their transaction/lock has been open too
> long. I am forced to disagree with your original statement.
>
> Kind Regards
> Paul Scott
> aspscott_at_tcp.co.uk
> ^^ remove 'as' anti-spam prefix to E-mail
Received on Fri Jan 15 1999 - 16:13:57 CST