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

And that, Rick, is one heckuva lot more graceful than I would have been with your response, which was neither helpful, technically astute, on topic, or polite.

Paul, try this: see if you can dump the ITL from the dba pertaining to the blocked transaction. This is not a solution, but a possible path toward one.

You'll want to do this on the offended server itself, and it'll get kinda real timey.

As to why Oracle can't help, the answer may really be as simple as they can't help. Sad but true.

best of luck.

Ross

>> 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?
>Rick, that really isn't the case at all ;o). It is a simple request
>on the world's best RDBMS (Oracle) but it can't seem to be done. I've
>had some superb E-mail replies from people who obviously know what
>they are talking about, and have had some extremely innovative
>alternative locking approaches. I've also had plenty of requests from
>others who want to know what the solution is, because they use the
>same locking techniques.
>
>But people are avoiding the question which exists within a bounded
>scenario. All I need is a query to join the locker SID to the refused
>locker SID after a pessimistic Nowait record lock. That is what I'm
>asking for.
>
>>If so I guess you've
>>probably got more of a problem than you think....
><Laughing> I know the lock problem is a big one, but as for me....
>thanks for the vote of confidence.
>
>>Rick:-)
>
>Kind Regards
>Paul Scott
>aspscott_at_tcp.co.uk
>^^ remove 'as' anti-spam prefix to E-mail
>
Received on Sun Jan 17 1999 - 00:20:11 CST