Re: Autonomous transactions and deadlocks
- From: Hans Forbrich <fuzzy.graybeard@xxxxxxxxx>
- To: rajugaru.vij@xxxxxxxxx
- Date: Mon, 25 Mar 2013 07:43:04 -0600
Look in detail at how locking works when updating bitmap indexes. (See
Richard Foote's blog, as a great resource for this.)
If you are updating the bitmap column, you are shooting yourself in the
foot as it is well known that updating a bitmap locks many, many, many
rows. (Possibly, but not necessarily all rows in the table.) So you
have one row locked, and you fire off an AT that wants to lock all sorts
of rows, but is waiting for your first session to release the lock on
that one row.
Again, describe your requirement in detail if you want potential
solutions or workarounds. Until then, we will be restricted to
describing possible scenarios.
/Hans
On 25/03/2013 7:13 AM, rajugaru.vij@xxxxxxxxx wrote:
> Version 10g R2..
>
> AT when working with bitmap index..
>
--
//www.freelists.org/webpage/oracle-l
Other related posts:
