本文探讨了SQL查询优化策略及其在并行处理环境下的应用，通过实例展示了如何提高查询效率并降低资源消耗。
select a.sid,a.serial#,a.status,a.last_call_et,b.type,d.OWNER,d.OBJECT_NAME,d.OBJECT_TYPE
from dba_objects d,v$session a,v$lock b,v$locked_object c
where a.sid=b.sid
and b.sid=c.session_id
and c.object_id=d.object_id
and b.type='TX'
and a.status='INACTIVE'
and a.last_call_et>600
union all
select a.sid,a.serial#,a.status,a.last_call_et,b.type,d.OWNER,d.OBJECT_NAME,d.OBJECT_TYPE
from dba_objects@dblink d,v$session@dblink a,v$lock@dblink b,v$locked_object@dblink c
where a.sid=b.sid
and b.sid=c.session_id
and c.object_id=d.object_id
and b.type='TX'
and a.status='INACTIVE'
and a.last_call_et>600
from dba_objects d,v$session a,v$lock b,v$locked_object c
where a.sid=b.sid
and b.sid=c.session_id
and c.object_id=d.object_id
and b.type='TX'
and a.status='INACTIVE'
and a.last_call_et>600
union all
select a.sid,a.serial#,a.status,a.last_call_et,b.type,d.OWNER,d.OBJECT_NAME,d.OBJECT_TYPE
from dba_objects@dblink d,v$session@dblink a,v$lock@dblink b,v$locked_object@dblink c
where a.sid=b.sid
and b.sid=c.session_id
and c.object_id=d.object_id
and b.type='TX'
and a.status='INACTIVE'
and a.last_call_et>600
扫一扫
731
被折叠的 条评论
为什么被折叠?
到【灌水乐园】发言
