Re: DFS lock wait
- From: Riyaj Shamsudeen <riyaj.shamsudeen@xxxxxxxxx>
- To: rjamya@xxxxxxxxx
- Date: Sun, 9 Oct 2011 11:46:18 -0500
Hello Raj
You probably know this, but this is a new feature (11.2) in which XA
transactions span across multiple instances with GTX background process
(btw, this leads to interesting side effects). If you are not using this new
feature, I don't see an issue disabling the feature.
I am sure, this is probably a bug, but if you aren't sure, try disabling
the feature and test it.
Cheers
Riyaj Shamsudeen
Principal DBA,
Ora!nternals - http://www.orainternals.com - Specialists in Performance,
RAC and EBS11i
Blog: http://orainternals.wordpress.com
Oracle ACE Director and OakTable member http://www.oaktable.com
Co-author of the books: Expert Oracle
Practices<http://tinyurl.com/book-expert-oracle-practices/>,
Pro Oracle SQL, Expert PL/SQL
Practices<http://tinyurl.com/book-expert-plsql-practices>
On Thu, Oct 6, 2011 at 7:17 AM, rjamya <rjamya@xxxxxxxxx> wrote:
> Also forgot to add, We do use XA but all sessions for that app _always_
> connect to a single node. That is how app is partitioned.
> Raj
>
> On Thu, Oct 6, 2011 at 8:00 AM, rjamya <rjamya@xxxxxxxxx> wrote:
>
> > Single Record View As of: 10/6/2011 7:51:43 AM
> > EVENT: DFS lock handle
> > P1TEXT: type|mode
> > P1: 1146617861
> > P1RAW: 0000000044580005
> > P2TEXT: id1
> > P2: 3376176309
> > P2RAW: 00000000C93C5CB5
> > P3TEXT: id2
> > P3: 0
> > P3RAW: 00
> > WAIT_CLASS_ID: 1893977003
> > WAIT_CLASS#: 0
> > WAIT_CLASS: Other
> > WAIT_TIME: 0
> > SECONDS_IN_WAIT: 0
> > STATE: WAITING
> >
> > The lock is always DX or BB and mode is always 5.
> >
> > Raj
> > On Thu, Oct 6, 2011 at 7:43 AM, <jonathan@xxxxxxxxxxxxxxxxxx> wrote:
> >
> >>
> >> What's the actual lock for ? (in other words, what's the p1raw value)
> >>
> >> Regards
> >> Jonathan Lewis
> >>
> >>
>
>
> --
> -----
> Best regards
> Raj
>
>
> --
> //www.freelists.org/webpage/oracle-l
>
>
>
--
//www.freelists.org/webpage/oracle-l
Other related posts:
