[Xymon] dbcheck.pl bug with locks check, comments, suggestion welcome

[Gore, David W (David)]

We really like the dbcheck.pl script and its ability to monitor remote databases.  Unfortunately, the check caused a number of databases to become unreachable and complain about temp space, oracle errors ORA-01114 and ORA-27063.  Perhaps someone with a bit more database experience than I can verify the veracity of this statement used for blocking in the dbcheck.pl script:

$selcmd{oracle}{locks}=qq#select l1.id1 "id1", l1.id2 "id2", l2.id1 "id3", l2.id2 "id4", l1.sid "sid1", l2.sid "sid2", l1.type "type1", l2.type "type2", l1.request "request1", l2.request "request2", l1.lmode "mode1", l2.lmode "mode2", l1.ctime "ctime1", l2.ctime "ctime2" from v\$lock l1, v\$lock l2 where l1.BLOCK=1 and l2.request > 0 and l1.id1 =l2.id1 and l2.id2 = l2.id2# ;

The last bit of the where clause is what I think is suspect:

l1.id1 =l2.id1 and l2.id2 = l2.id2
-------------------^^
----------------------------^^

SHOULD BE:

l1.id1 =l2.id1 and l1.id2 = l2.id2
-------------------^^
----------------------------^^

Any database experts out there? 


~David