Re: UPDATE fails- deadlock? -- simultaneous access to DB

From: Isaac Blank <izblank_at_yahoo.com>
Date: Wed, 07 May 2003 19:26:05 GMT
Message-ID: <h5dua.36$jF7.6354157@newssvr21.news.prodigy.com>

    Yes, making sure all transactions update tables in the same order (and only once per transaction) will eliminate deadlocks. The overall throughput will stii suffer, because sessions will be effectively serialized due to locking caused by contention.

    You should identify hot spots (points of contention) and minimize (better yet, eradicate) such occurences. It's hard to make any specific recommendations without knowing any particulars. In general:

- make sure your transactions are only as long as necessary.
- make sure different sessions do not modify same rows in the database
- talk to DBAs and see if the tablespaces have INITRANS and MAXTRANS big

enough for the concurrensy level you have.

"Padmashali" <g_padmashali_at_yahoo.com> wrote in message news:3ebd7b0d.0305061627.4e776aac_at_posting.google.com...
> We are facing the DB dead-lock problem. Multiple Access to tables are
> required. More than one transactions are trying to access the same
> table and DB deadlock is noticed.
>
> Will the order of access the Tables will resolve the problem, if I
> provide controlled access to each table in a particular order.
>
> Request you all to suggest various methodology/approach to prevent
> such scenario.
>
> Its Very Urgent.
>
> Thank You Very Much
>
> Best Regards
> Padmashali
Received on Wed May 07 2003 - 14:26:05 CDT