I have created TM lock in oracle 9i and 11g databases. by using same query

Question

here is the query uesd for finding a lock in database.
select /*+ RULE */ 'DATAPOINT # ' bpb,
l.sid, ' # ',
s.username, ' # ',
s.sql_address, ' # ',
x.sid, ' # ',
y.username, ' # ',
l.type, ' # ',
l.id1, ' # ',
l.id2, ' # ',
decode(X.LMODE,
0, 'None',
1, 'Null',
2, 'Row Share',
3, 'Row Excl',
4, 'Share',
5, 'Shr Row Excl',
6, 'Exclusive',
decode(L.REQUEST,
0, 'None',
1, 'Null',
2, 'Row Share',
3, 'Row Excl',
4, 'Share',
5, 'Shr Row Excl',
6, 'Exclusive',
from v$session s, v$lock l, v$lock x, v$session y
where l.ctime > 120
and s.lockwait = l.kaddr
and l.type in ('TM', 'TX', 'UL')
and l.id1 = x.id1
and l.id2 = x.id2
and x.sid != l.sid
and x.sid = y.sid
and x.lmode >0;
after doing further investigation i found that for 11g condition s.lockwait = l.kaddr not satisfied where as for 9i it's gives correct results
here are the lockwait and kaddr values for 9i and 11g databases.
for oracle 9i
SQL> select lockwait from v$session where sid in (10,12);
LOCKWAIT
67B4E10C
SQL> select kaddr from v$lock where sid in (10,12);
KADDR
67B4E088
67B4E10C
for oracle 11g
SQL> select lockwait from v$session where sid in (70,134);
LOCKWAIT
070000002FA080D8
SQL> select kaddr from v$lock where sid in (70,134);
KADDR
0700000030C595C0
0700000030C59830
00000001108E3E58
00000001108E3E58
070000002FA6CB30
SQL>
please advise if there is any change for calculations for lockwait,kaddr for 11g.

Answer 1

can you post your query with explain plan for both 9i version and 10g version.
Thanks,
karthick.