RE: PowerBuilder & Oracle Locking--HELP!!!!
From: <as360114_at_orion.yorku.ca>
Date: 1995/04/06
Message-ID: <1995Apr6.172915.1_at_orion.yorku.ca>#1/1
>
> This can happen in ORACLE if you are using foreign keys without
> indexes over them. If table A has a primary key and then table B
> references the primary key with no index, then deleting a row in table
> A will result in a share table lock on table B.
>
> The solution is to always create an index over any foreign key.
>
> Regards,
> Michael Harvey (mgh_at_world.net)
>
Date: 1995/04/06
Message-ID: <1995Apr6.172915.1_at_orion.yorku.ca>#1/1
In article <3m0q01$c3i_at_world.net>, mgh_at_ausnet.world.net (Michael Harvey) writes:
> In article <3luhjl$nbk_at_linus.mitre.org>, vv_at_mbunix.mitre.org says...
>>
>>We are using Oracle 7.0.16 and Powerbuilder and getting shared table
locks
>>which keep other users from updating and occasionally lead to deadlocks. >>Has anyone had a similar experience? The developers claim that they >>are not doing this--and a Powerbuilder "expert" says it's notPowerbuilder.
>> >>Any clues in netland??? >>
>
> This can happen in ORACLE if you are using foreign keys without
> indexes over them. If table A has a primary key and then table B
> references the primary key with no index, then deleting a row in table
> A will result in a share table lock on table B.
>
> The solution is to always create an index over any foreign key.
>
> Regards,
> Michael Harvey (mgh_at_world.net)
>
Is that a bug with Oracle, or an un-documented feature?
Ramy Taraboulsi. Received on Thu Apr 06 1995 - 00:00:00 CEST