Could this be caused by the well known issue of a non-indexed foreign key
causing an entire table to be locked?
Frank Bucher <frankbucher_at_gmx.de> wrote in message
news:f742146.0202210638.3a4d9d25_at_posting.google.com...
> Hi all,
> we're running 8.1.7.2 server on an AIX machine and have 8.1.5 clients
> on NT machines. The discussion that appears is, that if oracle does
> some kind of row locking. We have one table 'customer' (which is a
> parent table to several other ones). On this table a transaction holds
> a lock (row exclusive), because a client worked with a customer
> (insert/update). Could it be that oracle locks other customer as well
> for an insert or an update? It seems that other the clients couldn't
> work with other customers as well. Therefore it seems as if oracle
> tries to lock a whole block?! Does this behaviour depend on the kind
> of activity (insert or update)? How does an insert on a table affect
> locks at all, if it has no foreign keys?
>
> Any help appreciated.
>
> TIA
> Frank.
>
> PS: Could you please mail the answer as well to frankbucher_at_gmx.de
Received on Thu Feb 21 2002 - 14:25:30 CST
