Re: Locking Problem

Mike,

Thanks for this. It certainly looks possible - the table that I think is the problem is set with INITRANS 1 and PCTFREE 10 so there's not much extra space in the block to play with.

My question now is, is there any way that I can quickly check that this is the situation that's happening? Is there a dba view which I can use to convince myself and the client's DBA staff that this is the problem?

Presumably, the only way to remedy the situation is going to be to re-create the table and then get the data back from a temporary table or an export - all fairly timeconsuming and not really something I want to do unless I know I'll get some improvements.

Thanks

Mike Burden wrote in message <36DD07B0.67055814_at_capgemini.co.uk>...
>Setting a correct value for initrans is important.
>
>When initrans space is not available it is the only time Oracle locks at
block
>level as oppose to row level. This can cause transactions which use no keys
in
>common with another transaction to lock out each other.
>
>The default value for initrans is one so only enough space if reserved for
a
>single user. More space will be used but only if it is available. If it's
not
>you will lock the block. This can lead to deadlocks.
>
Received on Mon Mar 08 1999 - 10:15:29 CST