开发反映执行一条sql很慢,查看问题时发现,第一次执行很快,后续执行很慢,等待无结果,只好中断
对应sql语句为
select o.merchant_no,
o.mer_order_id,
o.bank_name,
o.account_no,
o.account_name,
o.cert_type,
o.cert_no,
o.tran_amt,
o.msg_ext,
o.create_time,
o.update_time,
o.merchant_resp_code,
o.merchant_resp_desc
from cp_order_flow o,
(select k.khm
from (select count(1), t.hash_msg khm
from cp_order_flow t
where t.create_time between
to_date('20160926050000', 'yyyyMMddhh24miss') and
to_date('20160926120000', 'yyyyMMddhh24miss')
and t.tran_code = 'TC1002'
and (to_number(t.update_time - t.create_time) * 24 * 60 * 60 > 30 or
t.state = '03')
group by t.hash_msg
having count(1) > 1) k) p
where o.hash_msg = p.khm
and o.create_time between to_date('20160926050000', 'yyyyMMddhh24miss') and
to_date('20160926120000', 'yyyyMMddhh24miss')
order by o.account_no, o.account_name, o.create_time;
使用select * from table(dbms_xplan.display_cursor('1ukkmp54t9bkr',null,'advanced'));查看sql执行计划
发现sql有两个版本的执行计划
对于第二个执行计划,在note部分有“cardinality feedback used for this statement”,表示使用了基数反馈(Cardinality Feedback)
基数反馈(Cardinality Feedback)是 Oracle 11.2 中引入的新特性,主要针对统计信息旧、无直方图或有直方图但仍基数计算不准确的情况,Cardinality 基数的计算直接影响到后续的 JOIN COST 等重要的成本计算评估,造成 CBO 选择错误的执行计划。但是该参数存在不稳定因素,可能会带来执行效率的问题,建议关闭
alter system set "_optimizer_use_feedback"=FALSE;
此处先在session级别关闭
alter session set "_optimizer_use_feedback"=FALSE;
接下来反复执行sql,发现执行时间恢复正常