Re: DX Lock in index
Date: Tue, 28 Apr 2009 15:19:01 +0200
I understand that part, but why would the lock be registered against an index? My understanding from the developers is that this lock on an index was blocking. That is what confuses me, why would we get an index level lock of type DX?
My current understaning is that the report on this was invalid. There was another locking issue and it was reported to me as being the DX locks, while the real issue was a normal local TX lock in the DB.
We'll see if this surfaces again.
On Tue, Apr 28, 2009 at 2:48 PM, Vamshi Damidi <vamshireddy_1_at_hotmail.com>wrote:
> hi mathias,
> this is related to distributed locking mechanism
> check your code logic once again it acquiring a lock on remote database and
> has to be commited or rolled back for the trasaction to complete on remote
> Vamshi .D
> *From:* Mathias Magnusson <mathias.magnusson_at_gmail.com>
> *Sent:* Tuesday, April 28, 2009 8:09 AM
> *To:* oracle-l <oracle-l_at_freelists.org>
> *Subject:* DX Lock in index
> I have just encountered a situation where we get blocking locks on indexes
> where the locktype is DX. I didn't think blocking occured on index for
> regular SQL. Does anyone recognize this or know of a document that goes into
> detail on DX locks. I'm not finding much detail on this locktype.
> I don't have a current lock situation to pull data from, but last time the
> locked object seemed to map to an index. Isn't DX supposed to be a
> transaction lock controlling the undo and other things required for a remote
> incomming transaction? That is, should I expect it to block data and/or
> index? I'm mostly looking for verification that the current conclusion that
> this was in an index is unlikely and we need to track the lock next time to
> try to find a target more natural for DX.