Kill the Blocker

Question

Hi all,
11.2.0.1
We have been long bothered by a blocking process that prevents our batch process to successfully complete during midnight.
This script helped me to identify the blocker, but did not provide the serial#r for killing the process.
select distinct s1.username ||'@'|| s1.machine ||'(INST=' || s1.inst_id ||' SID= '|| s1.sid ||')
is blocking '|| s2.username || '@' || s2.machine || ' (INST=' || s1.inst_id||' SID='||s2.sid ||')'    
AS blocking_status, s2.program,s3.sql_id, s3.sql_text from gv$lock l1, gv$session s1, gv$lock l2, gv$session s2, v$sql s3
    where s1.sid=l1.sid
    and s2.sid=l2.sid
    and l1.block=1
    and l2.request >0
    and l1.id1=l2.id1
    and l2.id2=l2.id2
    and s2.sql_id = s3.sql_id;
It this regard, to prove that I am not "lazy" I am revising the script and tell me if it correct by testing at your respective db.
Here is my revised script:
select distinct 'alter system kill session '||''''||s1.sid||','||s1.serial#||',@'||s1.inst_id||'''' from gv$lock l1, gv$session s1, gv$lock l2, gv$session s2, v$sql s3
    where s1.sid=l1.sid
    and s2.sid=l2.sid
    and l1.block=1
    and l2.request >0
    and l1.id1=l2.id1
    and l2.id2=l2.id2
    and s2.sql_id = s3.sql_id;
Please check it it will kill the right process?
Thanks a lot,
zxy

Answer 1

yxes2013 wrote:
You did not check it
You did not even noticed the redundant conditions which Nicolas has observed.
    and l2.id2=l2.id2
Please check if it can be removed or there has been substitute or overwritten conditions missing?
Thanks
Troll.