<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>惜分飞 &#187; Oracle性能优化</title>
	<atom:link href="https://www.xifenfei.com/category/database/oracle/performance-optimization/feed" rel="self" type="application/rss+xml" />
	<link>https://www.xifenfei.com</link>
	<description>提供7*24专业数据库(Oracle,SQL Server,MySQL,PostgreSQL等)恢复和技术支持@Tel:17813235971</description>
	<lastBuildDate>Sat, 07 Nov 2026 15:45:44 +0000</lastBuildDate>
	<language>zh-CN</language>
		<sy:updatePeriod>hourly</sy:updatePeriod>
		<sy:updateFrequency>1</sy:updateFrequency>
	
	<item>
		<title>failed parse elapsed time过大分析案例</title>
		<link>https://www.xifenfei.com/2019/06/failed-parse-elapsed-time.html</link>
		<comments>https://www.xifenfei.com/2019/06/failed-parse-elapsed-time.html#comments</comments>
		<pubDate>Tue, 11 Jun 2019 14:54:47 +0000</pubDate>
		<dc:creator><![CDATA[惜分飞]]></dc:creator>
				<category><![CDATA[Oracle性能优化]]></category>
		<category><![CDATA[failed parse elapsed time]]></category>

		<guid isPermaLink="false">https://www.xifenfei.com/?p=8135</guid>
		<description><![CDATA[联系：手机/微信(+86 17813235971) QQ(107644445)  &#8230; <a href="https://www.xifenfei.com/2019/06/failed-parse-elapsed-time.html">继续阅读 <span class="meta-nav">&#8594;</span></a>]]></description>
				<content:encoded><![CDATA[<div id="xifenfeicopyright">
<p>联系：<a href="https://www.xifenfei.com/about_xifenfei" target="_blank">手机/微信(+86 17813235971)   QQ(107644445)</a><a target="_blank" href="http://wpa.qq.com/msgrd?v=3&#038;uin=107644445&#038;site=qq&#038;menu=yes"><img src="https://www.xifenfei.com/wp-content/themes/img/site_qq.jpg" alt="QQ咨询惜分飞" title="QQ咨询惜分飞"/></a></p>
<p>标题：<a href="https://www.xifenfei.com/2019/06/failed-parse-elapsed-time.html" target="_blank">failed parse elapsed time过大分析案例</a></p>
<p>作者：<a href="https://www.xifenfei.com" target="_blank">惜分飞</a>©版权所有[未经本人同意,不得以任何形式转载,否则有进一步追究法律责任的权利.]</p>
</div>
<p>朋友公司做压力测试,awr比较异常,让给看看<br />
<a href="//www.xifenfei.com/wp-content/uploads/2019/06/1-1.jpg"><img src="//www.xifenfei.com/wp-content/uploads/2019/06/1-1.jpg" alt="1-1" width="620" height="104" class="alignnone size-full wp-image-8136" /></a><br />
<hr />
这里显示数据库db time较大,数据库应该比较繁忙,主要等待事件为:library cache: mutex X<br />
<a href="//www.xifenfei.com/wp-content/uploads/2019/06/1-4.jpg"><img src="//www.xifenfei.com/wp-content/uploads/2019/06/1-4.jpg" alt="1-4" width="462" height="151" class="alignnone size-full wp-image-8138" /></a><br />
<hr />
但是Load Profile显示Parses (SQL)和Hard parses (SQL)均不大<br />
<a href="//www.xifenfei.com/wp-content/uploads/2019/06/1-2.jpg"><img src="//www.xifenfei.com/wp-content/uploads/2019/06/1-2.jpg" alt="1-2" width="631" height="420" class="alignnone size-full wp-image-8137" /></a><br />
<hr />
但是发现failed parse elapsed time特别大,也就是说这个库出现该问题,主要可能是由于sql语句执行解析失败导致,而解析失败最大的可能性就是sql语句语法/权限错误.对于这类问题可以通过设置event 10035进行跟踪<br />
<a href="//www.xifenfei.com/wp-content/uploads/2019/06/1-3.jpg"><img src="//www.xifenfei.com/wp-content/uploads/2019/06/1-3.jpg" alt="1-3" width="670" height="376" class="alignnone size-full wp-image-8139" /></a><br />
<hr />
演示设置event 10035进行跟踪的效果</p>
<pre class="brush: sql; title: ; notranslate">
SQL&gt; select * from v$version;

BANNER
--------------------------------------------------------------------------------
Oracle Database 11g Enterprise Edition Release 11.2.0.4.0 - 64bit Production
PL/SQL Release 11.2.0.4.0 - Production
CORE    11.2.0.4.0      Production
TNS for 64-bit Windows: Version 11.2.0.4.0 - Production
NLSRTL Version 11.2.0.4.0 - Production

SQL&gt; ALTER SYSTEM SET EVENTS '10035 trace name context forever, level 1';

System altered.

SQL&gt; ALTER SESSION SET EVENTS '10035 trace name context forever, level 1';

Session altered.

SQL&gt; select 1;
select 1
       *
ERROR at line 1:
ORA-00923: FROM keyword not found where expected


SQL&gt; select * from xifenfei_t;
select * from xifenfei_t
              *
ERROR at line 1:
ORA-00942: table or view does not exist
</pre>
<p>查看alert日志,观察错误语句<br />
<a href="//www.xifenfei.com/wp-content/uploads/2019/06/1-5.jpg"><img src="//www.xifenfei.com/wp-content/uploads/2019/06/1-5.jpg" alt="1-5" width="926" height="248" class="alignnone size-full wp-image-8140" /></a><br />
<hr />
<div id="crp_related"><ul><li style="list-style-type:decimal;font-size:11px;" ><a href="https://www.xifenfei.com/2019/07/savemydataqq-com-recovery.html" rel="bookmark" class="crp_title">savemydata@qq.com加密数据库恢复</a></li><li style="list-style-type:decimal;font-size:11px;" ><a href="https://www.xifenfei.com/2019/11/oracle-dmp-is-encrypted-recovery.html" rel="bookmark" class="crp_title">oracle dmp被加密恢复</a></li><li style="list-style-type:decimal;font-size:11px;" ><a href="https://www.xifenfei.com/2019/11/sql-server-drop-recovery.html" rel="bookmark" class="crp_title">SQL Server drop table 恢复</a></li><li style="list-style-type:decimal;font-size:11px;" ><a href="https://www.xifenfei.com/2019/11/sql-server-delete-recovery.html" rel="bookmark" class="crp_title">SQL Server delete恢复</a></li><li style="list-style-type:decimal;font-size:11px;" ><a href="https://www.xifenfei.com/2019/09/win-rman-shared-directory.html" rel="bookmark" class="crp_title">rman备份到win共享目录</a></li><li style="list-style-type:decimal;font-size:11px;" ><a href="https://www.xifenfei.com/2019/05/id-decrypt.html" rel="bookmark" class="crp_title">*** ALL YOUR WORK AND PERSONAL FILES HAVE BEEN ENCRYPTED ***</a></li><li style="list-style-type:decimal;font-size:11px;" ><a href="https://www.xifenfei.com/2019/11/file-encrypt-and-decrypt-database-recovery.html" rel="bookmark" class="crp_title">文件系统加密解密之后数据库异常处理</a></li><li style="list-style-type:decimal;font-size:11px;" ><a href="https://www.xifenfei.com/2019/12/megac-recovery.html" rel="bookmark" class="crp_title">.megac加密恢复</a></li><li style="list-style-type:decimal;font-size:11px;" ><a href="https://www.xifenfei.com/2019/12/xfs-rm-datafile-recovery.html" rel="bookmark" class="crp_title">xfs删除数据文件恢复</a></li><li style="list-style-type:decimal;font-size:11px;" ><a href="https://www.xifenfei.com/2019/11/sql-server-truncate-recovery.html" rel="bookmark" class="crp_title">SQL Server truncate table 恢复</a></li><li style="list-style-type:decimal;font-size:11px;" ><a href="https://www.xifenfei.com/2019/12/helpservishorsefucker-org-recovery.html" rel="bookmark" class="crp_title">helpservis@horsefucker.org加密恢复</a></li><li style="list-style-type:decimal;font-size:11px;" ><a href="https://www.xifenfei.com/2019/04/traceroute-has-a-disk-hb-but-no-network-hb.html" rel="bookmark" class="crp_title">has a disk HB, but no network HB&#8212;-traceroute不通导致</a></li></ul></div>]]></content:encoded>
			<wfw:commentRss>https://www.xifenfei.com/2019/06/failed-parse-elapsed-time.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>sql plan baseline简单介绍</title>
		<link>https://www.xifenfei.com/2019/04/sql-plan-baseline.html</link>
		<comments>https://www.xifenfei.com/2019/04/sql-plan-baseline.html#comments</comments>
		<pubDate>Fri, 05 Apr 2019 15:11:56 +0000</pubDate>
		<dc:creator><![CDATA[惜分飞]]></dc:creator>
				<category><![CDATA[Oracle性能优化]]></category>

		<guid isPermaLink="false">https://www.xifenfei.com/?p=8004</guid>
		<description><![CDATA[联系：手机/微信(+86 17813235971) QQ(107644445)  &#8230; <a href="https://www.xifenfei.com/2019/04/sql-plan-baseline.html">继续阅读 <span class="meta-nav">&#8594;</span></a>]]></description>
				<content:encoded><![CDATA[<div id="xifenfeicopyright">
<p>联系：<a href="https://www.xifenfei.com/about_xifenfei" target="_blank">手机/微信(+86 17813235971)   QQ(107644445)</a><a target="_blank" href="http://wpa.qq.com/msgrd?v=3&#038;uin=107644445&#038;site=qq&#038;menu=yes"><img src="https://www.xifenfei.com/wp-content/themes/img/site_qq.jpg" alt="QQ咨询惜分飞" title="QQ咨询惜分飞"/></a></p>
<p>标题：<a href="https://www.xifenfei.com/2019/04/sql-plan-baseline.html" target="_blank">sql plan baseline简单介绍</a></p>
<p>作者：<a href="https://www.xifenfei.com" target="_blank">惜分飞</a>©版权所有[未经本人同意,不得以任何形式转载,否则有进一步追究法律责任的权利.]</p>
</div>
<p>Oracle 11g开始，提供了一种新的固定执行计划的方法，即SQL plan baseline，中文名SQL执行计划基线（简称基线），可以认为是OUTLINE（大纲）或者SQL PROFILE的改进版本，基本上它的主要作用可以归纳为如下两个：<br />
1、稳定给定SQL语句的执行计划，防止执行环境或对象统计信息等因子的改变对SQL语句的执行计划产生影响<br />
2、减少数据库中出现SQL语句性能退化的概率，理论上不允许一条语句切换到一个比已经执行过的执行计划慢很多的新的执行计划上(可以通过OPTIMIZER_USE_SQL_PLAN_BASELINE实现)<br />
3、sql baseline对于sql 大小写，sql空格可以生效，但是对于非绑定变量sql，如果使用不同变量无法生效(无force_matching功能)<br />
<strong>确认当前无sql baseline启用</strong></p>
<pre class="brush: sql; title: ; notranslate">
SQL&gt; select sql_handle,plan_name,dbms_lob.substr(sql_text,60,1) sql_text,ACCEPTED from dba_sql_plan_baselines;

no rows selected
</pre>
<p><strong>创建场景</strong><br />
模拟一个表有index,如果再不强制的情况下,查询直接使用index,但是我这边要通过sql baseline模拟使用走全表扫描,实现不修改sql的情况下直接修改执行计划</p>
<pre class="brush: sql; title: ; notranslate">
SQL&gt; create table t_xifenfei tablespace users as select * from dba_objects;

Table created.

SQL&gt; create index i_xifenfei on t_xifenfei(object_id) tablespace users;

Index created.

SQL&gt; execute dbms_stats.gather_table_stats('SYS','T_XIFENFEI',CASCADE=&gt;TRUE);

PL/SQL procedure successfully completed.

SQL&gt; select OBJECT_NAME from T_XIFENFEI where OBJECT_ID=100;

OBJECT_NAME
--------------------------------------------------------------------------------------------------------------
ORA$BASE

SQL&gt; SELECT * FROM table(dbms_xplan.display_cursor);

PLAN_TABLE_OUTPUT
--------------------------------------------------------------------------------------------------------------
SQL_ID  b9hj14ntjgmtr, child number 0
-------------------------------------
select OBJECT_NAME from T_XIFENFEI where OBJECT_ID=100

Plan hash value: 1926396081

------------------------------------------------------------------------------------------
| Id  | Operation                   | Name       | Rows  | Bytes | Cost (%CPU)| Time     |
------------------------------------------------------------------------------------------
|   0 | SELECT STATEMENT            |            |       |       |     2 (100)|          |
|   1 |  TABLE ACCESS BY INDEX ROWID| T_XIFENFEI |     1 |    30 |     2   (0)| 00:00:01 |
|*  2 |   INDEX RANGE SCAN          | I_XIFENFEI |     1 |       |     1   (0)| 00:00:01 |
------------------------------------------------------------------------------------------

Predicate Information (identified by operation id):
---------------------------------------------------

   2 - access(&quot;OBJECT_ID&quot;=100)


19 rows selected.


SQL&gt; select /*+FULL(T_XIFENFEI)*/OBJECT_NAME from T_XIFENFEI where OBJECT_ID=100;

OBJECT_NAME
--------------------------------------------------------------------------------------------------------------
ORA$BASE

SQL&gt; SELECT * FROM table(dbms_xplan.display_cursor);

PLAN_TABLE_OUTPUT
--------------------------------------------------------------------------------------------------------------
SQL_ID  aqgv7stwu6w5t, child number 0
-------------------------------------
select /*+FULL(T_XIFENFEI)*/OBJECT_NAME from T_XIFENFEI where
OBJECT_ID=100

Plan hash value: 548923532

--------------------------------------------------------------------------------
| Id  | Operation         | Name       | Rows  | Bytes | Cost (%CPU)| Time     |
--------------------------------------------------------------------------------
|   0 | SELECT STATEMENT  |            |       |       |   349 (100)|          |
|*  1 |  TABLE ACCESS FULL| T_XIFENFEI |     1 |    30 |   349   (1)| 00:00:05 |
--------------------------------------------------------------------------------

Predicate Information (identified by operation id):
---------------------------------------------------

   1 - filter(&quot;OBJECT_ID&quot;=100)


19 rows selected.
</pre>
<p><strong>从shared pool->library cache中直接加载sql plan baseline</strong></p>
<pre class="brush: sql; title: ; notranslate">
SQL&gt; set serveroutput on
SQL&gt;  DECLARE
  2      ret PLS_INTEGER;
  3    BEGIN
  4      ret := dbms_spm.load_plans_from_cursor_cache(sql_id          =&gt; 'b9hj14ntjgmtr',
  5                                                   plan_hash_value =&gt; null);
  6      dbms_output.put_line(ret || ' SQL plan baseline(s) created');
  7    END;
  8    /
1 SQL plan baseline(s) created

PL/SQL procedure successfully completed.

SQL&gt; select sql_handle,plan_name,dbms_lob.substr(sql_text,60,1) sql_text,ACCEPTED from dba_sql_plan_baselines;

SQL_HANDLE                     PLAN_NAME
------------------------------ ------------------------------
SQL_TEXT
--------------------------------------------------------------------------------------------------------------
ACC
---
SQL_ed6b78bdb7b643ad           SQL_PLAN_fuuvsrqvvchxd04acd9ab
select OBJECT_NAME from T_XIFENFEI where OBJECT_ID=100
YES

SQL&gt; select * from table(dbms_xplan.display_cursor('b9hj14ntjgmtr','',''));

PLAN_TABLE_OUTPUT
--------------------------------------------------------------------------------------------------------------
SQL_ID  b9hj14ntjgmtr, child number 1
-------------------------------------
select OBJECT_NAME from T_XIFENFEI where OBJECT_ID=100

Plan hash value: 1926396081

------------------------------------------------------------------------------------------
| Id  | Operation                   | Name       | Rows  | Bytes | Cost (%CPU)| Time     |
------------------------------------------------------------------------------------------
|   0 | SELECT STATEMENT            |            |       |       |     2 (100)|          |
|   1 |  TABLE ACCESS BY INDEX ROWID| T_XIFENFEI |     1 |    30 |     2   (0)| 00:00:01 |
|*  2 |   INDEX RANGE SCAN          | I_XIFENFEI |     1 |       |     1   (0)| 00:00:01 |
------------------------------------------------------------------------------------------

Predicate Information (identified by operation id):
---------------------------------------------------

   2 - access(&quot;OBJECT_ID&quot;=100)

Note
-----
   - SQL plan baseline SQL_PLAN_fuuvsrqvvchxd04acd9ab used for this statement


23 rows selected.
</pre>
<p><strong>利用第一个baseline的sql_handle创建新执行计划的baseline</strong></p>
<pre class="brush: sql; title: ; notranslate">
SQL&gt; set serveroutput on
SQL&gt; DECLARE
  2    ret pls_integer;
  3   begin
  4   ret := DBMS_SPM.LOAD_PLANS_FROM_CURSOR_CACHE (
  5   sql_id=&gt;'aqgv7stwu6w5t',
  6   plan_hash_value=&gt;548923532,sql_handle=&gt;'SQL_ed6b78bdb7b643ad'
  7   );
  8  dbms_output.put_line(ret || ' SQL plan baseline(s) created');
  9   end;
 10   /
1 SQL plan baseline(s) created

PL/SQL procedure successfully completed.

SQL&gt;  select sql_handle,plan_name,dbms_lob.substr(sql_text,60,1) sql_text,ACCEPTED from dba_sql_plan_baselines;

SQL_HANDLE                     PLAN_NAME
------------------------------ ------------------------------
SQL_TEXT
--------------------------------------------------------------------------------------------------------------
ACC
---
SQL_ed6b78bdb7b643ad           SQL_PLAN_fuuvsrqvvchxd04acd9ab
select OBJECT_NAME from T_XIFENFEI where OBJECT_ID=100
YES

SQL_ed6b78bdb7b643ad           SQL_PLAN_fuuvsrqvvchxdf0c521d1
select OBJECT_NAME from T_XIFENFEI where OBJECT_ID=100
YES
</pre>
<p><strong>删除第一个baseline</strong></p>
<pre class="brush: sql; title: ; notranslate">
SQL&gt; set serveroutput on
SQL&gt; DECLARE
  2    ret pls_integer;
  3   begin
  4   ret := DBMS_SPM.drop_sql_plan_baseline (  sql_handle=&gt;'SQL_ed6b78bdb7b643ad'
     ,plan_name=&gt;'SQL_PLAN_fuuvsrqvvchxd04acd9ab');
  5  dbms_output.put_line(ret || ' SQL plan baseline(s) created');
  6   end;
  7   /
1 SQL plan baseline(s) created

PL/SQL procedure successfully completed.


SQL&gt; select sql_handle,plan_name,dbms_lob.substr(sql_text,60,1) sql_text,ACCEPTED from dba_sql_plan_baselines;

SQL_HANDLE                     PLAN_NAME
------------------------------ ------------------------------
SQL_TEXT
--------------------------------------------------------------------------------------------------------------
ACC
---
SQL_ed6b78bdb7b643ad           SQL_PLAN_fuuvsrqvvchxdf0c521d1
select OBJECT_NAME from T_XIFENFEI where OBJECT_ID=100
YES
</pre>
<p><strong>验证baseline生效，实现sql语句执行计划的改变</strong></p>
<pre class="brush: sql; title: ; notranslate">
SQL&gt; alter system flush shared_pool;

System altered.

SQL&gt; select OBJECT_NAME from T_XIFENFEI where OBJECT_ID=100;

OBJECT_NAME
--------------------------------------------------------------------------------------------------------------
ORA$BASE

SQL&gt;  select * from table(dbms_xplan.display_cursor('b9hj14ntjgmtr','',''));

PLAN_TABLE_OUTPUT
--------------------------------------------------------------------------------------------------------------
SQL_ID  b9hj14ntjgmtr, child number 1
-------------------------------------
select OBJECT_NAME from T_XIFENFEI where OBJECT_ID=100

Plan hash value: 548923532

--------------------------------------------------------------------------------
| Id  | Operation         | Name       | Rows  | Bytes | Cost (%CPU)| Time     |
--------------------------------------------------------------------------------
|   0 | SELECT STATEMENT  |            |       |       |   349 (100)|          |
|*  1 |  TABLE ACCESS FULL| T_XIFENFEI |     1 |    30 |   349   (1)| 00:00:05 |
--------------------------------------------------------------------------------

Predicate Information (identified by operation id):
---------------------------------------------------

   1 - filter(&quot;OBJECT_ID&quot;=100)

Note
-----
   - SQL plan baseline SQL_PLAN_fuuvsrqvvchxdf0c521d1 used for this statement


22 rows selected.
</pre>
<p><strong>利用coe脚本利用baseline快速绑定sql执行计划</strong></p>
<pre class="brush: sql; title: ; notranslate">
SQL&gt; set serveroutput on
SQL&gt; DECLARE
  2    ret pls_integer;
  3   begin
  4   ret := DBMS_SPM.drop_sql_plan_baseline (  sql_handle=&gt;'SQL_ed6b78bdb7b643ad',
      plan_name=&gt;'SQL_PLAN_fuuvsrqvvchxdf0c521d1');
  5  dbms_output.put_line(ret || ' SQL plan baseline(s) created');
  6   end;
  7   /
1 SQL plan baseline(s) created

PL/SQL procedure successfully completed.

SQL&gt; select sql_handle,plan_name,dbms_lob.substr(sql_text,60,1) sql_text,ACCEPTED from dba_sql_plan_baselines;

no rows selected


SQL&gt; alter system flush shared_pool;

System altered.

SQL&gt; select OBJECT_NAME from T_XIFENFEI where OBJECT_ID=100;

OBJECT_NAME
--------------------------------------------------------------------------------------------------------------
ORA$BASE

SQL&gt; select /*+FULL(T_XIFENFEI)*/OBJECT_NAME from T_XIFENFEI where OBJECT_ID=100;

OBJECT_NAME
--------------------------------------------------------------------------------------------------------------
ORA$BASE

SQL&gt; select sql_id,sql_text from v$sql where sql_text like '%from T_XIFENFEI where OBJECT_ID=100%';

SQL_ID
-------------
SQL_TEXT
--------------------------------------------------------------------------------------------------------------
aqgv7stwu6w5t
select /*+FULL(T_XIFENFEI)*/OBJECT_NAME from T_XIFENFEI where OBJECT_ID=100

7jdqvvnpxb9z5
select sql_id,sql_text from v$sql where sql_text like '%from T_XIFENFEI where OBJECT_ID=100%'

b9hj14ntjgmtr
select OBJECT_NAME from T_XIFENFEI where OBJECT_ID=100


SQL&gt; select sql_id,PLAN_HASH_VALUE from v$sql where sql_id in('b9hj14ntjgmtr','aqgv7stwu6w5t');

SQL_ID        PLAN_HASH_VALUE
------------- ---------------
aqgv7stwu6w5t       548923532
b9hj14ntjgmtr      1926396081

SQL&gt;  select * from table(dbms_xplan.display_cursor('aqgv7stwu6w5t','',''));

PLAN_TABLE_OUTPUT
--------------------------------------------------------------------------------------------------------------
SQL_ID  aqgv7stwu6w5t, child number 0
-------------------------------------
select /*+FULL(T_XIFENFEI)*/OBJECT_NAME from T_XIFENFEI where
OBJECT_ID=100

Plan hash value: 548923532

--------------------------------------------------------------------------------
| Id  | Operation         | Name       | Rows  | Bytes | Cost (%CPU)| Time     |
--------------------------------------------------------------------------------
|   0 | SELECT STATEMENT  |            |       |       |   349 (100)|          |
|*  1 |  TABLE ACCESS FULL| T_XIFENFEI |     1 |    30 |   349   (1)| 00:00:05 |
--------------------------------------------------------------------------------

Predicate Information (identified by operation id):
---------------------------------------------------

   1 - filter(&quot;OBJECT_ID&quot;=100)


19 rows selected.

SQL&gt;  select * from table(dbms_xplan.display_cursor('b9hj14ntjgmtr','',''));

PLAN_TABLE_OUTPUT
--------------------------------------------------------------------------------------------------------------
SQL_ID  b9hj14ntjgmtr, child number 0
-------------------------------------
select OBJECT_NAME from T_XIFENFEI where OBJECT_ID=100

Plan hash value: 1926396081

------------------------------------------------------------------------------------------
| Id  | Operation                   | Name       | Rows  | Bytes | Cost (%CPU)| Time     |
------------------------------------------------------------------------------------------
|   0 | SELECT STATEMENT            |            |       |       |     2 (100)|          |
|   1 |  TABLE ACCESS BY INDEX ROWID| T_XIFENFEI |     1 |    30 |     2   (0)| 00:00:01 |
|*  2 |   INDEX RANGE SCAN          | I_XIFENFEI |     1 |       |     1   (0)| 00:00:01 |
------------------------------------------------------------------------------------------

Predicate Information (identified by operation id):
---------------------------------------------------

   2 - access(&quot;OBJECT_ID&quot;=100)


19 rows selected.




SQL&gt; @coe_load_sql_baseline.sql

Parameter 1:
ORIGINAL_SQL_ID (required)

Enter value for 1: b9hj14ntjgmtr

Parameter 2:
MODIFIED_SQL_ID (required)

Enter value for 2: aqgv7stwu6w5t


     PLAN_HASH_VALUE          AVG_ET_SECS
-------------------- --------------------
           548923532                 .003

Parameter 3:
PLAN_HASH_VALUE (required)

Enter value for 3: 548923532



SQL&gt; select sql_handle,plan_name,dbms_lob.substr(sql_text,60,1) sql_text,ACCEPTED from dba_sql_plan_baselines;

SQL_HANDLE                     PLAN_NAME
------------------------------ ------------------------------
SQL_TEXT
--------------------------------------------------------------------------------
ACC
---
SQL_ed6b78bdb7b643ad           SQL_PLAN_fuuvsrqvvchxdf0c521d1
select OBJECT_NAME from T_XIFENFEI where OBJECT_ID=100
YES


SQL&gt; alter system flush shared_pool ;

System altered.

SQL&gt; select OBJECT_NAME from T_XIFENFEI where OBJECT_ID=100;

OBJECT_NAME
--------------------------------------------------------------------------------
ORA$BASE

SQL&gt;  select * from table(dbms_xplan.display_cursor('b9hj14ntjgmtr','',''));

PLAN_TABLE_OUTPUT
--------------------------------------------------------------------------------
SQL_ID  b9hj14ntjgmtr, child number 1
-------------------------------------
select OBJECT_NAME from T_XIFENFEI where OBJECT_ID=100

Plan hash value: 548923532

--------------------------------------------------------------------------------
| Id  | Operation         | Name       | Rows  | Bytes | Cost (%CPU)| Time     |
--------------------------------------------------------------------------------
|   0 | SELECT STATEMENT  |            |       |       |   349 (100)|          |
|*  1 |  TABLE ACCESS FULL| T_XIFENFEI |     1 |    30 |   349   (1)| 00:00:05 |

PLAN_TABLE_OUTPUT
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------

Predicate Information (identified by operation id):
---------------------------------------------------

   1 - filter(&quot;OBJECT_ID&quot;=100)

Note
-----
   - SQL plan baseline SQL_PLAN_fuuvsrqvvchxdf0c521d1 used for this statement


22 rows selected.
</pre>
<p><strong>sql空格和大小写改变不影响baseline效果</strong></p>
<pre class="brush: sql; title: ; notranslate">
SQL&gt;  select * from table(dbms_xplan.display_cursor('dwfxd7x6kwx6u','',''));

PLAN_TABLE_OUTPUT
--------------------------------------------------------------------------------
SQL_ID  dwfxd7x6kwx6u, child number 1
-------------------------------------
select     OBJECT_NAME from T_XIFENFEI where OBJECT_ID=100

Plan hash value: 548923532

--------------------------------------------------------------------------------
| Id  | Operation         | Name       | Rows  | Bytes | Cost (%CPU)| Time     |
--------------------------------------------------------------------------------
|   0 | SELECT STATEMENT  |            |       |       |   349 (100)|          |
|*  1 |  TABLE ACCESS FULL| T_XIFENFEI |     1 |    30 |   349   (1)| 00:00:05 |

PLAN_TABLE_OUTPUT
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------

Predicate Information (identified by operation id):
---------------------------------------------------

   1 - filter(&quot;OBJECT_ID&quot;=100)

Note
-----
   - SQL plan baseline SQL_PLAN_fuuvsrqvvchxdf0c521d1 used for this statement


22 rows selected.

SQL&gt; select     OBJECT_NAME from T_xifenfei where OBJECT_ID=100;

OBJECT_NAME
--------------------------------------------------------------------------------
ORA$BASE

SQL&gt; select sql_id,sql_text from v$sql where sql_text like '%from T_xifenfei where OBJECT_ID=100%';

SQL_ID
-------------
SQL_TEXT
--------------------------------------------------------------------------------
5spn2x6ac44af
select sql_id,sql_text from v$sql where sql_text like '%from T_xifenfei where OB
JECT_ID=100%'

8tytmh8r6w80n
select     OBJECT_NAME from T_xifenfei where OBJECT_ID=100


SQL&gt;  select * from table(dbms_xplan.display_cursor('8tytmh8r6w80n','',''));

PLAN_TABLE_OUTPUT
--------------------------------------------------------------------------------
SQL_ID  8tytmh8r6w80n, child number 1
-------------------------------------
select     OBJECT_NAME from T_xifenfei where OBJECT_ID=100

Plan hash value: 548923532

--------------------------------------------------------------------------------
| Id  | Operation         | Name       | Rows  | Bytes | Cost (%CPU)| Time     |
--------------------------------------------------------------------------------
|   0 | SELECT STATEMENT  |            |       |       |   349 (100)|          |
|*  1 |  TABLE ACCESS FULL| T_XIFENFEI |     1 |    30 |   349   (1)| 00:00:05 |

PLAN_TABLE_OUTPUT
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------

Predicate Information (identified by operation id):
---------------------------------------------------

   1 - filter(&quot;OBJECT_ID&quot;=100)

Note
-----
   - SQL plan baseline SQL_PLAN_fuuvsrqvvchxdf0c521d1 used for this statement


22 rows selected.
</pre>
<p><strong>但是sql变量不一样导致baseline失效</strong></p>
<pre class="brush: sql; title: ; notranslate">
SQL&gt;  select * from table(dbms_xplan.display_cursor('fp9u8wkp5cuw1','',''));

PLAN_TABLE_OUTPUT
--------------------------------------------------------------------------------
SQL_ID  fp9u8wkp5cuw1, child number 0
-------------------------------------
select OBJECT_NAME from T_XIFENFEI where OBJECT_ID=101

Plan hash value: 1926396081

------------------------------------------------------------------------------------------

| Id  | Operation                   | Name       | Rows  | Bytes | Cost (%CPU)|
Time     |

PLAN_TABLE_OUTPUT
--------------------------------------------------------------------------------
------------------------------------------------------------------------------------------

|   0 | SELECT STATEMENT            |            |       |       |     2 (100)|         |
|   1 |  TABLE ACCESS BY INDEX ROWID| T_XIFENFEI |     1 |    30 |     2   (0)|00:00:01 |
|*  2 |   INDEX RANGE SCAN          | I_XIFENFEI |     1 |       |     1   (0)|
PLAN_TABLE_OUTPUT
--------------------------------------------------------------------------------
00:00:01 |

------------------------------------------------------------------------------------------


Predicate Information (identified by operation id):
---------------------------------------------------

   2 - access(&quot;OBJECT_ID&quot;=101)


19 rows selected.
</pre>
<div id="crp_related"><ul><li style="list-style-type:decimal;font-size:11px;" ><a href="https://www.xifenfei.com/2012/05/sql-profile-%e4%bd%bf%e7%94%a8.html" rel="bookmark" class="crp_title">sql profile 使用</a></li><li style="list-style-type:decimal;font-size:11px;" ><a href="https://www.xifenfei.com/2012/12/%e5%88%9b%e5%bb%ba%e6%94%af%e6%8c%81null-index.html" rel="bookmark" class="crp_title">创建包含null值index</a></li><li style="list-style-type:decimal;font-size:11px;" ><a href="https://www.xifenfei.com/2012/04/9i%e4%b8%ad%e6%b8%85%e9%99%a4%e7%89%b9%e5%ae%9a%e8%a1%a8%e7%9b%b8%e5%85%b3%e6%89%a7%e8%a1%8c%e8%ae%a1%e5%88%92.html" rel="bookmark" class="crp_title">9I中清除特定表相关执行计划</a></li><li style="list-style-type:decimal;font-size:11px;" ><a href="https://www.xifenfei.com/2012/04/%e6%89%a7%e8%a1%8c%e8%ae%a1%e5%88%92%e4%b8%ad%e5%b8%b8%e8%a7%81index%e8%ae%bf%e9%97%ae%e6%96%b9%e5%bc%8f.html" rel="bookmark" class="crp_title">执行计划中常见index访问方式</a></li><li style="list-style-type:decimal;font-size:11px;" ><a href="https://www.xifenfei.com/2011/09/10g%e6%96%b0%e5%a2%9e%e5%88%97%e6%96%b9%e5%bc%8f%e6%8c%87%e5%ae%9ahint.html" rel="bookmark" class="crp_title">10g新增列方式指定HINT</a></li><li style="list-style-type:decimal;font-size:11px;" ><a href="https://www.xifenfei.com/2012/06/optimizer_index_caching%e5%92%8coptimizer_index_cost_adj%e5%8f%82%e6%95%b0%e8%af%b4%e6%98%8e.html" rel="bookmark" class="crp_title">OPTIMIZER_INDEX_CACHING和OPTIMIZER_INDEX_COST_ADJ参数说明</a></li><li style="list-style-type:decimal;font-size:11px;" ><a href="https://www.xifenfei.com/2012/05/bind-variable-peeking-%e6%b5%8b%e8%af%95.html" rel="bookmark" class="crp_title">Bind Variable Peeking 测试</a></li><li style="list-style-type:decimal;font-size:11px;" ><a href="https://www.xifenfei.com/2012/04/hint%e6%8c%87%e5%ae%9aindex%e7%9a%84%e6%b7%b1%e5%85%a5%e7%90%86%e8%a7%a3.html" rel="bookmark" class="crp_title">hint指定index的深入理解</a></li><li style="list-style-type:decimal;font-size:11px;" ><a href="https://www.xifenfei.com/2017/06/_optimizer_null_aware_antijoin-not-in.html" rel="bookmark" class="crp_title">_optimizer_null_aware_antijoin和not in效率</a></li><li style="list-style-type:decimal;font-size:11px;" ><a href="https://www.xifenfei.com/2012/05/%e4%bd%bf%e7%94%a8dblink%e5%af%bc%e8%87%b4%e7%9a%84-opaque_transform.html" rel="bookmark" class="crp_title">使用dblink导致的/*+ OPAQUE_TRANSFORM */</a></li><li style="list-style-type:decimal;font-size:11px;" ><a href="https://www.xifenfei.com/2021/09/sys_op_c2c.html" rel="bookmark" class="crp_title">重现sql执行计划SYS_OP_C2C隐式转换</a></li><li style="list-style-type:decimal;font-size:11px;" ><a href="https://www.xifenfei.com/2015/06/sql-profile%e6%94%b9%e5%8f%98hint%e7%9a%84%e6%89%a7%e8%a1%8c%e8%ae%a1%e5%88%92%e4%bb%a5%e5%8f%8acoe%e8%84%9a%e6%9c%ac%e5%ae%9e%e7%8e%b0sql-id%e4%b8%ad%e6%97%a0plan-hash-value%e7%9a%84sql-profile.html" rel="bookmark" class="crp_title">sql profile改变hint的执行计划以及coe脚本实现sql id中无PLAN HASH VALUE的sql profile生成</a></li></ul></div>]]></content:encoded>
			<wfw:commentRss>https://www.xifenfei.com/2019/04/sql-plan-baseline.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>使用_unnest_subquery优化sql</title>
		<link>https://www.xifenfei.com/2018/05/_unnest_subquery.html</link>
		<comments>https://www.xifenfei.com/2018/05/_unnest_subquery.html#comments</comments>
		<pubDate>Thu, 17 May 2018 14:34:57 +0000</pubDate>
		<dc:creator><![CDATA[惜分飞]]></dc:creator>
				<category><![CDATA[Oracle性能优化]]></category>
		<category><![CDATA[_unnest_subquery]]></category>

		<guid isPermaLink="false">https://www.xifenfei.com/?p=7448</guid>
		<description><![CDATA[联系：手机/微信(+86 17813235971) QQ(107644445)  &#8230; <a href="https://www.xifenfei.com/2018/05/_unnest_subquery.html">继续阅读 <span class="meta-nav">&#8594;</span></a>]]></description>
				<content:encoded><![CDATA[<div id="xifenfeicopyright">
<p>联系：<a href="https://www.xifenfei.com/about_xifenfei" target="_blank">手机/微信(+86 17813235971)   QQ(107644445)</a><a target="_blank" href="http://wpa.qq.com/msgrd?v=3&#038;uin=107644445&#038;site=qq&#038;menu=yes"><img src="https://www.xifenfei.com/wp-content/themes/img/site_qq.jpg" alt="QQ咨询惜分飞" title="QQ咨询惜分飞"/></a></p>
<p>标题：<a href="https://www.xifenfei.com/2018/05/_unnest_subquery.html" target="_blank">使用_unnest_subquery优化sql</a></p>
<p>作者：<a href="https://www.xifenfei.com" target="_blank">惜分飞</a>©版权所有[未经本人同意,不得以任何形式转载,否则有进一步追究法律责任的权利.]</p>
</div>
<p>一个复杂的sql查询,使用了大量EXISTS和NOT EXISTS 关联导致sql执行效率低下,这里挑选出来最核心的部分进行演示</p>
<pre class="brush: sql; title: ; notranslate">
SQL&gt; explain plan for   select  
  2   a.aab034, a.aac001
  3    from si_dp.ac01_ac02 a
  4   where exists (select 1
  5            from ic40
  6           where aac001 = a.aac001
  7             and aae045 &lt;= '201803'
  8             and aae120 = '0')
  9     and not exists (select 1
 10            from ic15
 11           where aac001 = a.aac001
 12             and aae002 &lt;= '201803')
 13     and not EXISTS (select aab001
 14            from ab01
 15           where aab019 in ('91', '93')
 16             AND aab001 = a.aab001)
 17    and exists (select 1
 18            from ac13
 19           where aac001 = a.aac001
 20             and aae140 = '11'
 21             and aae114 in ('0', '1')
 22             and aae002 &lt;= '201803')
 23     AND EXISTS (SELECT 1
 24            FROM AC13
 25           WHERE AAC001 = A.AAC001
 26             and aae140 = '11'
 27             AND AAE143 = '02'
 28             AND AAE003 &lt; '201707'
 29             AND AAE002 BETWEEN '201801' AND '201803'
 30             and aae114 = '1')
 31     AND not EXISTS (SELECT 1
 32         FROM AC13
 33           WHERE AAC001 = A.AAC001
 34             and aae140 = '11'
 35          AND AAE002 &lt; '201801')
 36     AND not EXISTS (SELECT 1
 37            FROM ac02
 38           WHERE AAC001 = A.AAC001
 39             and aae140 = '11'
 40             AND AAE036 &lt; date '2018-1-1');
 
Explained.

Elapsed: 00:00:00.36

SQL&gt; select * from table (dbms_xplan.display);


PLAN_TABLE_OUTPUT
--------------------------------------------------------------------------------------------------------

-----------------------------------------------------------------------------------------------------
| Id  | Operation                         | Name               | Rows  | Bytes |TempSpc| Cost (%CPU)|
-----------------------------------------------------------------------------------------------------
|   0 | SELECT STATEMENT                  |                    |     1 |   202 |       | 11172   (2)|
|   1 |  NESTED LOOPS SEMI                |                    |     1 |   202 |       | 11172   (2)|
|   2 |   NESTED LOOPS ANTI               |                    |     1 |   175 |       | 11168   (2)|
|   3 |    NESTED LOOPS SEMI              |                    |     1 |   150 |       | 11164   (2)|
|   4 |     NESTED LOOPS ANTI             |                    |     1 |   126 |       | 11160   (2)|
|   5 |      NESTED LOOPS SEMI            |                    |     1 |   104 |       | 11158   (2)|
|   6 |       NESTED LOOPS ANTI           |                    |     1 |    67 |       | 11145   (2)|
|   7 |        HASH JOIN ANTI             |                    |     1 |    50 |  8640K| 11143   (2)|
|   8 |         TABLE ACCESS FULL         | AC01_AC02          |   245K|  5755K|       |   356   (2)|
|   9 |         TABLE ACCESS FULL         | AC02               |   559K|    13M|       |  9346   (2)|
|  10 |        TABLE ACCESS BY INDEX ROWID| AB01               |     2 |    34 |       |     2   (0)|
|  11 |         INDEX UNIQUE SCAN         | PK_AB01            |     1 |       |       |     1   (0)|
|  12 |       TABLE ACCESS BY INDEX ROWID | AC13               |   325K|    11M|       |    13   (0)|
|  13 |        INDEX RANGE SCAN           | I_AC13_AAE143      |   446 |       |       |     4   (0)|
|  14 |      INDEX RANGE SCAN             | PK_IC15            |  1771K|    37M|       |     2   (0)|
|  15 |     TABLE ACCESS BY INDEX ROWID   | IC40               |    17M|   395M|       |     4   (0)|
|  16 |      INDEX RANGE SCAN             | PK_IC40            |     1 |       |       |     3   (0)|
|  17 |    TABLE ACCESS BY INDEX ROWID    | AC13               |    51M|  1236M|       |     4   (0)|
|  18 |     INDEX RANGE SCAN              | RELATION_233112_FK |     3 |       |       |     3   (0)|
|  19 |   TABLE ACCESS BY INDEX ROWID     | AC13               |    52M|  1350M|       |     4   (0)|
|  20 |    INDEX RANGE SCAN               | RELATION_233112_FK |     3 |       |       |     3   (0)|
-----------------------------------------------------------------------------------------------------
</pre>
<p>这条sql,在一个10.2.0.3的系统中执行了十几个小时无法出结果,开发商反馈,该大部分客户的11.2的环境中,大概十几分钟出结果.从来没有遇到此类情况.让我们给他优化sql.看到这个sql,第一反应就是很可能大量的NESTED LOOPS效率低下,怀疑统计信息错误,结果收集完统计信息之后,执行计划依旧,我就在思考怎么调整sql,让其不这样大量嵌套执行.想起来的_unnest_subquery是控制子查询嵌套转换的,从9i开始默认为true,尝试设置为false测试.</p>
<pre class="brush: sql; title: ; notranslate">
SQL&gt; alter session set &quot;_unnest_subquery&quot;=false;

Session altered.

Elapsed: 00:00:00.00
SQL&gt; explain plan for   select 
  2   a.aab034, a.aac001
  3    from si_dp.ac01_ac02 a
  4   where exists (select 1
  5            from ic40
  6           where aac001 = a.aac001
  7             and aae045 &lt;= '201803'
  8             and aae120 = '0')
  9     and not exists (select 1
 10            from ic15
 11           where aac001 = a.aac001
 12             and aae002 &lt;= '201803')
 13     and not EXISTS (select aab001
 14            from ab01
 15           where aab019 in ('91', '93')
 16             AND aab001 = a.aab001)
 17    and exists (select 1
 18            from ac13
 19          where aac001 = a.aac001
 20             and aae140 = '11'
 21             and aae114 in ('0', '1')
 22             and aae002 &lt;= '201803')
 23     AND EXISTS (SELECT 1
 24            FROM AC13
 25           WHERE AAC001 = A.AAC001
 26             and aae140 = '11'
 27             AND AAE143 = '02'
 28             AND AAE003 &lt; '201707'
 29             AND AAE002 BETWEEN '201801' AND '201803'
 30             and aae114 = '1')
 31     AND not EXISTS (SELECT 1
 32            FROM AC13
 33           WHERE AAC001 = A.AAC001
 34             and aae140 = '11'
 35             AND AAE002 &lt; '201801')
 36     AND not EXISTS (SELECT 1
 37            FROM ac02
 38           WHERE AAC001 = A.AAC001
 39             and aae140 = '11'
 40             AND AAE036 &lt; date '2018-1-1');
Explained.

Elapsed: 00:00:00.07

SQL&gt; select * from table (dbms_xplan.display);


PLAN_TABLE_OUTPUT
-----------------------------------------------------------------------------------------------

-----------------------------------------------------------------------------------------------
| Id  | Operation                     | Name             | Rows  | Bytes |TempSpc| Cost (%CPU)|
-----------------------------------------------------------------------------------------------
|   0 | SELECT STATEMENT              |                  |   185K|    19M|       |  2991K  (2)|
|   1 |  FILTER                       |                  |       |       |       |            |
|   2 |   HASH JOIN RIGHT SEMI        |                  |   185K|    19M|    16M|   758K  (3)|
|   3 |    TABLE ACCESS BY INDEX ROWID| AC13             |   353K|    12M|       |  4556   (1)|
|   4 |     INDEX SKIP SCAN           | I_AC13_AAB001    | 23608 |       |       |  2287   (1)|
|   5 |    HASH JOIN SEMI             |                  |   201K|    14M|    11M|   751K  (3)|
|   6 |     HASH JOIN SEMI            |                  |   201K|  9452K|  8640K|   123K  (3)|
|   7 |      TABLE ACCESS FULL        | AC01_AC02        |   245K|  5755K|       |   357   (2)|
|   8 |      TABLE ACCESS FULL        | IC40             |    21M|   481M|       | 86122   (3)|
|   9 |     TABLE ACCESS FULL         | AC13             |    52M|  1350M|       |   530K  (3)|
|  10 |   INDEX RANGE SCAN            | PK_IC15          |     2 |    44 |       |     3   (0)|
|  11 |   VIEW                        | index$_join$_009 |     1 |    17 |       |     3  (34)|
|  12 |    HASH JOIN                  |                  |       |       |       |            |
|  13 |     INDEX RANGE SCAN          | PK_AB01          |     1 |    17 |       |     2   (0)|
|  14 |     INLIST ITERATOR           |                  |       |       |       |            |
|  15 |      INDEX RANGE SCAN         | IDX_AB01_AAB019  |     1 |    17 |       |     8   (0)|
|  16 |   TABLE ACCESS BY INDEX ROWID | AC13             |     2 |    50 |       |     5   (0)|
|  17 |    INDEX RANGE SCAN           | I_AC13_SEARCH    |   152 |       |       |     4   (0)|
|  18 |   TABLE ACCESS BY INDEX ROWID | AC02             |     1 |    26 |       |     4   (0)|
|  19 |    INDEX RANGE SCAN           | PK_AC02          |     1 |       |       |     3   (0)|
-----------------------------------------------------------------------------------------------
</pre>
<p>让开发设置该参数,然后执行sql,结果3分钟不到出结果,非常圆满完成任务.该sql还有进一步优化空间,但是考虑到已经满足要求,不再折腾.</p>
<div id="crp_related"><ul><li style="list-style-type:decimal;font-size:11px;" ><a href="https://www.xifenfei.com/2010/12/oracle%e8%a1%a8%e4%b8%89%e7%a7%8d%e9%93%be%e6%8e%a5.html" rel="bookmark" class="crp_title">oracle表三种链接</a></li><li style="list-style-type:decimal;font-size:11px;" ><a href="https://www.xifenfei.com/2011/09/10g%e6%96%b0%e5%a2%9e%e5%88%97%e6%96%b9%e5%bc%8f%e6%8c%87%e5%ae%9ahint.html" rel="bookmark" class="crp_title">10g新增列方式指定HINT</a></li><li style="list-style-type:decimal;font-size:11px;" ><a href="https://www.xifenfei.com/2014/03/%e5%90%abis-null-sql%e8%af%ad%e5%8f%a5%e4%bc%98%e5%8c%96.html" rel="bookmark" class="crp_title">含is null sql语句优化</a></li><li style="list-style-type:decimal;font-size:11px;" ><a href="https://www.xifenfei.com/2012/06/optimizer_index_caching%e5%92%8coptimizer_index_cost_adj%e5%8f%82%e6%95%b0%e8%af%b4%e6%98%8e.html" rel="bookmark" class="crp_title">OPTIMIZER_INDEX_CACHING和OPTIMIZER_INDEX_COST_ADJ参数说明</a></li><li style="list-style-type:decimal;font-size:11px;" ><a href="https://www.xifenfei.com/2012/01/obj%e5%9d%8f%e5%9d%97%e6%83%85%e5%86%b5%e4%b8%8bexp%e5%af%bc%e5%87%ba%e5%8d%95%e4%b8%aa%e8%a1%a8%e8%a7%a3%e5%86%b3%e6%96%b9%e6%a1%88.html" rel="bookmark" class="crp_title">obj$坏块情况下exp导出单个表解决方案</a></li><li style="list-style-type:decimal;font-size:11px;" ><a href="https://www.xifenfei.com/2011/09/oracle-ddl-%e5%b9%b6%e5%8f%9110g.html" rel="bookmark" class="crp_title">Oracle DDL 并行(10G)</a></li><li style="list-style-type:decimal;font-size:11px;" ><a href="https://www.xifenfei.com/2014/10/11g%e4%b8%ad-connect-by-%e8%af%ad%e5%8f%a5%e6%89%a7%e8%a1%8c%e8%ae%a1%e5%88%92%e6%94%b9%e5%8f%98.html" rel="bookmark" class="crp_title">11g中 connect by 语句执行计划改变</a></li><li style="list-style-type:decimal;font-size:11px;" ><a href="https://www.xifenfei.com/2011/09/oracle-dml%e5%b9%b6%e5%8f%91.html" rel="bookmark" class="crp_title">Oracle DML并行</a></li><li style="list-style-type:decimal;font-size:11px;" ><a href="https://www.xifenfei.com/2019/04/sql-plan-baseline.html" rel="bookmark" class="crp_title">sql plan baseline简单介绍</a></li><li style="list-style-type:decimal;font-size:11px;" ><a href="https://www.xifenfei.com/2012/05/sql-profile-%e4%bd%bf%e7%94%a8.html" rel="bookmark" class="crp_title">sql profile 使用</a></li><li style="list-style-type:decimal;font-size:11px;" ><a href="https://www.xifenfei.com/2015/05/oracle-12c-table-access-by-index-rowid-batched.html" rel="bookmark" class="crp_title">Oracle 12C TABLE ACCESS BY INDEX ROWID BATCHED</a></li><li style="list-style-type:decimal;font-size:11px;" ><a href="https://www.xifenfei.com/2012/04/hint%e6%8c%87%e5%ae%9aindex%e7%9a%84%e6%b7%b1%e5%85%a5%e7%90%86%e8%a7%a3.html" rel="bookmark" class="crp_title">hint指定index的深入理解</a></li></ul></div>]]></content:encoded>
			<wfw:commentRss>https://www.xifenfei.com/2018/05/_unnest_subquery.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>数据文件自扩展引起&#8212;enq: HW &#8211; contention</title>
		<link>https://www.xifenfei.com/2018/04/enq-hw-contention.html</link>
		<comments>https://www.xifenfei.com/2018/04/enq-hw-contention.html#comments</comments>
		<pubDate>Mon, 02 Apr 2018 09:40:35 +0000</pubDate>
		<dc:creator><![CDATA[惜分飞]]></dc:creator>
				<category><![CDATA[Oracle性能优化]]></category>
		<category><![CDATA[enq: HW - contention]]></category>

		<guid isPermaLink="false">https://www.xifenfei.com/?p=7353</guid>
		<description><![CDATA[联系：手机/微信(+86 17813235971) QQ(107644445)  &#8230; <a href="https://www.xifenfei.com/2018/04/enq-hw-contention.html">继续阅读 <span class="meta-nav">&#8594;</span></a>]]></description>
				<content:encoded><![CDATA[<div id="xifenfeicopyright">
<p>联系：<a href="https://www.xifenfei.com/about_xifenfei" target="_blank">手机/微信(+86 17813235971)   QQ(107644445)</a><a target="_blank" href="http://wpa.qq.com/msgrd?v=3&#038;uin=107644445&#038;site=qq&#038;menu=yes"><img src="https://www.xifenfei.com/wp-content/themes/img/site_qq.jpg" alt="QQ咨询惜分飞" title="QQ咨询惜分飞"/></a></p>
<p>标题：<a href="https://www.xifenfei.com/2018/04/enq-hw-contention.html" target="_blank">数据文件自扩展引起&#8212;enq: HW &#8211; contention</a></p>
<p>作者：<a href="https://www.xifenfei.com" target="_blank">惜分飞</a>©版权所有[未经本人同意,不得以任何形式转载,否则有进一步追究法律责任的权利.]</p>
</div>
<p>客户反馈数据库比较慢,严重影响业务运行,让我们进行分析<br />
<strong>enq: HW &#8211; contention等待明显</strong><br />
登录上去查看发现大量的enq: HW &#8211; contention等相关等待.<br />
<a href="//www.xifenfei.com"><img src="//www.xifenfei.com/wp-content/uploads/2018/04/1.jpg" alt="1" width="1320" height="675" class="alignleft size-full wp-image-7354" /></a><br />
<a href="//www.xifenfei.com/wp-content/uploads/2018/04/2.jpg"><img src="//www.xifenfei.com/wp-content/uploads/2018/04/2.jpg" alt="2" width="970" height="348" class="alignleft size-full wp-image-7355" /></a><br />
<hr />
<strong>确认相关对象</strong></p>
<pre class="brush: sql; title: ; notranslate">
SQL&gt; select p3 from v$session_wait where event = 'enq: HW - contention';

   P3 
----------
34083635

SQL&gt; select dbms_utility.data_block_address_block(34083635) RDBA_FILE,
  2  dbms_utility.data_block_address_file(34083635) RDBA_BLOCK from dual;  

 RDBA_FILE RDBA_BLOCK
---------- ----------
    529203          8


SQL&gt;  select owner, segment_type, segment_name,tablespace_name   
  2      from dba_extents   
  3      where file_id = 8   
  4     and 529203 between block_id and block_id + blocks - 1;  

   OWNER   SEGMENT_TYPE        SEGMENT_NAME 	    TABLESPACE_NAME
---------- ------------------- -------------------  -------------------
XXXX       INDEX               T_TRADEITEM_85        USERS
</pre>
<p><strong>确认对应sql</strong><br />
<a href="//www.xifenfei.com/wp-content/uploads/2018/04/3.jpg"><img src="//www.xifenfei.com/wp-content/uploads/2018/04/3.jpg" alt="3" width="1108" height="214" class="alignleft size-full wp-image-7356" /></a><br />
<hr />
<strong>分析表空间使用情况</strong><br />
<a href="//www.xifenfei.com/wp-content/uploads/2018/04/4.jpg"><img src="//www.xifenfei.com/wp-content/uploads/2018/04/4.jpg" alt="4" width="1427" height="300" class="alignleft size-full wp-image-7357" /></a><br />
<hr />
<strong>增加数据文件</strong><br />
<a href="//www.xifenfei.com/wp-content/uploads/2018/04/5.jpg"><img src="//www.xifenfei.com/wp-content/uploads/2018/04/5.jpg" alt="5" width="1094" height="96" class="alignleft size-full wp-image-7358" /></a><br />
<hr />
<strong>再次查询表空间使用情况</strong><br />
<a href="//www.xifenfei.com/wp-content/uploads/2018/04/6.jpg"><img src="//www.xifenfei.com/wp-content/uploads/2018/04/6.jpg" alt="6" width="1383" height="287" class="alignleft size-full wp-image-7359" /></a><br />
<hr />
<strong>查询等待事件</strong><br />
<a href="//www.xifenfei.com/wp-content/uploads/2018/04/71.jpg"><img src="//www.xifenfei.com/wp-content/uploads/2018/04/71.jpg" alt="7" width="1251" height="256" class="alignleft size-full wp-image-7362" /></a><br />
<hr />
通过这里的分析,由于USERS表空间的空闲表空间已经被完全使用,后续使用需要扩展,因而引起了enq: HW &#8211; contention等待,以及由于该等待引起了其他相关等待,当users表空间进行扩展之后,立马恢复正常.实际的例子证明,<strong>在实际生产中特别是高并发生产库中,数据文件自扩展会严重影响数据库性能</strong>.</p>
<div id="crp_related"><ul><li style="list-style-type:decimal;font-size:11px;" ><a href="https://www.xifenfei.com/2018/11/file-system-corruption-oracle-recovery.html" rel="bookmark" class="crp_title">文件系统损坏导致数据文件异常恢复</a></li><li style="list-style-type:decimal;font-size:11px;" ><a href="https://www.xifenfei.com/2018/04/alco-recovery.html" rel="bookmark" class="crp_title">.ALCO 比特币加密勒索恢复</a></li><li style="list-style-type:decimal;font-size:11px;" ><a href="https://www.xifenfei.com/2018/04/chak1-recovery.html" rel="bookmark" class="crp_title">.CHAK1 比特币加密勒索恢复</a></li><li style="list-style-type:decimal;font-size:11px;" ><a href="https://www.xifenfei.com/2018/08/asm-disk-size-limit.html" rel="bookmark" class="crp_title">asm disk 大小限制</a></li><li style="list-style-type:decimal;font-size:11px;" ><a href="https://www.xifenfei.com/2016/01/vmware-vsphere6-0-%e5%88%9d%e8%af%95.html" rel="bookmark" class="crp_title">VMware vSphere6.0 初试</a></li><li style="list-style-type:decimal;font-size:11px;" ><a href="https://www.xifenfei.com/2013/04/oracle-7-3-4-%e6%88%aa%e5%9b%be%e6%ac%a3%e8%b5%8f.html" rel="bookmark" class="crp_title">ORACLE 7.3.4 截图欣赏</a></li><li style="list-style-type:decimal;font-size:11px;" ><a href="https://www.xifenfei.com/2025/10/linux7-8-single-user.html" rel="bookmark" class="crp_title">redhat系列7/8进入单用户模式</a></li><li style="list-style-type:decimal;font-size:11px;" ><a href="https://www.xifenfei.com/2011/11/oracle-8i%e5%ae%89%e8%a3%85%e6%88%aa%e5%9b%be.html" rel="bookmark" class="crp_title">Oracle 8i安装过程截图</a></li><li style="list-style-type:decimal;font-size:11px;" ><a href="https://www.xifenfei.com/2018/10/gandcrab-v5-0-4-recovery.html" rel="bookmark" class="crp_title">GANDCRAB V5.0.4 比特币加密oracle数据库恢复</a></li><li style="list-style-type:decimal;font-size:11px;" ><a href="https://www.xifenfei.com/2018/11/ogg-vlogfile-frequent-query.html" rel="bookmark" class="crp_title">ogg导致v$logfile查询频繁</a></li><li style="list-style-type:decimal;font-size:11px;" ><a href="https://www.xifenfei.com/2015/11/windows-listener-log-4g.html" rel="bookmark" class="crp_title">windows平台listener.log超过4G导致监听异常</a></li><li style="list-style-type:decimal;font-size:11px;" ><a href="https://www.xifenfei.com/2025/12/sql-bak-0-lost-data.html" rel="bookmark" class="crp_title">模拟sql server故障备份完成恢复实现数据0丢失</a></li></ul></div>]]></content:encoded>
			<wfw:commentRss>https://www.xifenfei.com/2018/04/enq-hw-contention.html/feed</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>_optimizer_null_aware_antijoin和not in效率</title>
		<link>https://www.xifenfei.com/2017/06/_optimizer_null_aware_antijoin-not-in.html</link>
		<comments>https://www.xifenfei.com/2017/06/_optimizer_null_aware_antijoin-not-in.html#comments</comments>
		<pubDate>Sun, 04 Jun 2017 05:26:22 +0000</pubDate>
		<dc:creator><![CDATA[惜分飞]]></dc:creator>
				<category><![CDATA[Oracle性能优化]]></category>
		<category><![CDATA[not in]]></category>
		<category><![CDATA[_optimizer_null_aware_antijoin]]></category>

		<guid isPermaLink="false">https://www.xifenfei.com/?p=7128</guid>
		<description><![CDATA[联系：手机/微信(+86 17813235971) QQ(107644445)  &#8230; <a href="https://www.xifenfei.com/2017/06/_optimizer_null_aware_antijoin-not-in.html">继续阅读 <span class="meta-nav">&#8594;</span></a>]]></description>
				<content:encoded><![CDATA[<div id="xifenfeicopyright">
<p>联系：<a href="https://www.xifenfei.com/about_xifenfei" target="_blank">手机/微信(+86 17813235971)   QQ(107644445)</a><a target="_blank" href="http://wpa.qq.com/msgrd?v=3&#038;uin=107644445&#038;site=qq&#038;menu=yes"><img src="https://www.xifenfei.com/wp-content/themes/img/site_qq.jpg" alt="QQ咨询惜分飞" title="QQ咨询惜分飞"/></a></p>
<p>标题：<a href="https://www.xifenfei.com/2017/06/_optimizer_null_aware_antijoin-not-in.html" target="_blank">_optimizer_null_aware_antijoin和not in效率</a></p>
<p>作者：<a href="https://www.xifenfei.com" target="_blank">惜分飞</a>©版权所有[未经本人同意,不得以任何形式转载,否则有进一步追究法律责任的权利.]</p>
</div>
<p><strong>准备两个测试表</strong></p>
<pre class="brush: sql; title: ; notranslate">
SQL&gt; conn chf/oracle
Connected.
SQL&gt; select * from v$version;

BANNER
----------------------------------------------------------------------------
Oracle Database 11g Enterprise Edition Release 11.2.0.4.0 - 64bit Production
PL/SQL Release 11.2.0.4.0 - Production
CORE    11.2.0.4.0      Production
TNS for Linux: Version 11.2.0.4.0 - Production
NLSRTL Version 11.2.0.4.0 - Production

SQL&gt; create table t_xifenfei
  2  as select * from dba_objects;

Table created.

SQL&gt; select count(*) from t_xifenfei;

  COUNT(*)
----------
     86259

SQL&gt; create table t_xifenfei1
  2  as select * from dba_objects;

Table created.

SQL&gt; select count(*) from t_xifenfei1;

  COUNT(*)
----------
     86260

--删除部分记录，用来做not in的内部表
SQL&gt; delete from t_xifenfei where object_id&gt;86200;

918 rows deleted.

SQL&gt; commit;

Commit complete.
</pre>
<p><strong>查询_optimizer_null_aware_antijoin隐含参数默认值</strong></p>
<pre class="brush: sql; title: ; notranslate">
SQL&gt; conn / as sysdba
Connected.
SQL&gt; col name for a52
SQL&gt; col value for a24
SQL&gt; col description for a50
set linesize 150
select a.ksppinm name,b.ksppstvl value,a.ksppdesc description
  from x$ksppi a,x$ksppcv b
 where a.inst_id = USERENV ('Instance')
   and b.inst_id = USERENV ('Instance')
   and a.indx = b.indx
   and upper(a.ksppinm) LIKE upper('%&amp;param%')
order by name
SQL&gt; SQL&gt;   2    3    4    5    6    7    8  /
Enter value for param: _optimizer_null_aware_antijoin
old   6:    and upper(a.ksppinm) LIKE upper('%&amp;param%')
new   6:    and upper(a.ksppinm) LIKE upper('%_optimizer_null_aware_antijoin%')

NAME                                                 VALUE                    DESCRIPTION
---------------------------------------------------- ------------------------ -----------------------------
_optimizer_null_aware_antijoin                       TRUE                     null-aware antijoin parameter
</pre>
<p>_optimizer_null_aware_antijoin从11.1.0.6开始引进,默认为true<br />
<br />
<strong>_optimizer_null_aware_antijoin为true,执行not in</strong></p>
<pre class="brush: sql; title: ; notranslate">
SQL&gt; conn chf/oracle 
Connected.
SQL&gt; set autot trace
SQL&gt; set timing on
SQL&gt; set lines 150
SQL&gt; set pages 1000
SQL&gt;  select count(*) from t_xifenfei1 where object_id not in(select object_id from t_xifenfei);

Elapsed: 00:00:00.09

Execution Plan
----------------------------------------------------------
Plan hash value: 4048525918

----------------------------------------------------------------------------------------
| Id  | Operation                | Name        | Rows  | Bytes | Cost (%CPU)| Time     |
----------------------------------------------------------------------------------------
|   0 | SELECT STATEMENT         |             |     1 |    10 |   688   (1)| 00:00:09 |
|   1 |  SORT AGGREGATE          |             |     1 |    10 |            |          |
|*  2 |   HASH JOIN RIGHT ANTI NA|             |  1137 | 11370 |   688   (1)| 00:00:09 |
|   3 |    TABLE ACCESS FULL     | T_XIFENFEI  | 85341 |   416K|   344   (1)| 00:00:05 |
|   4 |    TABLE ACCESS FULL     | T_XIFENFEI1 | 86260 |   421K|   344   (1)| 00:00:05 |
----------------------------------------------------------------------------------------

Predicate Information (identified by operation id):
---------------------------------------------------

   2 - access(&quot;OBJECT_ID&quot;=&quot;OBJECT_ID&quot;)


Statistics
----------------------------------------------------------
          1  recursive calls
          0  db block gets
       2472  consistent gets
          0  physical reads
          0  redo size
        527  bytes sent via SQL*Net to client
        520  bytes received via SQL*Net from client
          2  SQL*Net roundtrips to/from client
          0  sorts (memory)
          0  sorts (disk)
          1  rows processed
</pre>
<p><strong>_optimizer_null_aware_antijoin为false,执行not in</strong></p>
<pre class="brush: sql; title: ; notranslate">
SQL&gt; alter session set &quot;_optimizer_null_aware_antijoin&quot;=false;

Session altered.

Elapsed: 00:00:00.00
SQL&gt; select count(*) from t_xifenfei1 where object_id not in(select object_id from t_xifenfei);

Elapsed: 00:02:29.64

Execution Plan
----------------------------------------------------------
Plan hash value: 2503880249

-----------------------------------------------------------------------------------
| Id  | Operation           | Name        | Rows  | Bytes | Cost (%CPU)| Time     |
-----------------------------------------------------------------------------------
|   0 | SELECT STATEMENT    |             |     1 |     5 |    25M  (1)| 86:20:57 |
|   1 |  SORT AGGREGATE     |             |     1 |     5 |            |          |
|*  2 |   FILTER            |             |       |       |            |          |
|   3 |    TABLE ACCESS FULL| T_XIFENFEI1 | 86260 |   421K|   344   (1)| 00:00:05 |
|*  4 |    TABLE ACCESS FULL| T_XIFENFEI  |     1 |     5 |   344   (1)| 00:00:05 |
-----------------------------------------------------------------------------------

Predicate Information (identified by operation id):
---------------------------------------------------

   2 - filter( NOT EXISTS (SELECT 0 FROM &quot;T_XIFENFEI&quot; &quot;T_XIFENFEI&quot; WHERE
              LNNVL(&quot;OBJECT_ID&quot;&lt;&gt;:B1)))
   4 - filter(LNNVL(&quot;OBJECT_ID&quot;&lt;&gt;:B1))


Statistics
----------------------------------------------------------
          0  recursive calls
          0  db block gets
   52982891  consistent gets
          0  physical reads
          0  redo size
        527  bytes sent via SQL*Net to client
        520  bytes received via SQL*Net from client
          2  SQL*Net roundtrips to/from client
          0  sorts (memory)
          0  sorts (disk)
          1  rows processed
</pre>
<p>这里很明显,当 _optimizer_null_aware_antijoin为false的时候not in效率非常低(当in里面记录多，使用FILTER效率肯定低下).<br />
<br />
<strong>_optimizer_null_aware_antijoin为false,执行not exists</strong></p>
<pre class="brush: sql; title: ; notranslate">
SQL&gt; alter session set &quot;_optimizer_null_aware_antijoin&quot;=false;

Session altered.

SQL&gt;select count(*) from t_xifenfei1 b where not exists 
 2  (select 1 from t_xifenfei a where a.object_id=b.object_id);

Elapsed: 00:00:00.07

Execution Plan
----------------------------------------------------------
Plan hash value: 2976307246

-------------------------------------------------------------------------------------
| Id  | Operation             | Name        | Rows  | Bytes | Cost (%CPU)| Time     |
-------------------------------------------------------------------------------------
|   0 | SELECT STATEMENT      |             |     1 |    10 |   688   (1)| 00:00:09 |
|   1 |  SORT AGGREGATE       |             |     1 |    10 |            |          |
|*  2 |   HASH JOIN RIGHT ANTI|             |  1137 | 11370 |   688   (1)| 00:00:09 |
|   3 |    TABLE ACCESS FULL  | T_XIFENFEI  | 85341 |   416K|   344   (1)| 00:00:05 |
|   4 |    TABLE ACCESS FULL  | T_XIFENFEI1 | 86260 |   421K|   344   (1)| 00:00:05 |
-------------------------------------------------------------------------------------

Predicate Information (identified by operation id):
---------------------------------------------------

   2 - access(&quot;A&quot;.&quot;OBJECT_ID&quot;=&quot;B&quot;.&quot;OBJECT_ID&quot;)


Statistics
----------------------------------------------------------
          0  recursive calls
          0  db block gets
       2472  consistent gets
          0  physical reads
          0  redo size
        527  bytes sent via SQL*Net to client
        520  bytes received via SQL*Net from client
          2  SQL*Net roundtrips to/from client
          0  sorts (memory)
          0  sorts (disk)
          1  rows processed
</pre>
<p>对于11g的版本可以通过_optimizer_null_aware_antijoin参数开启NULL-aware Anti join特性来提高not in的效率,对于11g以下版本可以通过not exists来提高效率</p>
<div id="crp_related"><ul><li style="list-style-type:decimal;font-size:11px;" ><a href="https://www.xifenfei.com/2012/04/%e6%89%a7%e8%a1%8c%e8%ae%a1%e5%88%92%e4%b8%ad%e5%b8%b8%e8%a7%81index%e8%ae%bf%e9%97%ae%e6%96%b9%e5%bc%8f.html" rel="bookmark" class="crp_title">执行计划中常见index访问方式</a></li><li style="list-style-type:decimal;font-size:11px;" ><a href="https://www.xifenfei.com/2012/12/%e5%88%9b%e5%bb%ba%e6%94%af%e6%8c%81null-index.html" rel="bookmark" class="crp_title">创建包含null值index</a></li><li style="list-style-type:decimal;font-size:11px;" ><a href="https://www.xifenfei.com/2013/04/12c-top-n-sql%e5%ae%9e%e7%8e%b0%e5%88%86%e9%a1%b5%e5%8a%9f%e8%83%bd.html" rel="bookmark" class="crp_title">ORACLE 12C TOP N SQL实现分页功能</a></li><li style="list-style-type:decimal;font-size:11px;" ><a href="https://www.xifenfei.com/2015/05/oracle-12c-table-access-by-index-rowid-batched.html" rel="bookmark" class="crp_title">Oracle 12C TABLE ACCESS BY INDEX ROWID BATCHED</a></li><li style="list-style-type:decimal;font-size:11px;" ><a href="https://www.xifenfei.com/2011/07/select-maxamina-from-table%e4%bc%98%e5%8c%96.html" rel="bookmark" class="crp_title">select max(id),min(id) from table优化</a></li><li style="list-style-type:decimal;font-size:11px;" ><a href="https://www.xifenfei.com/2012/05/bind-variable-peeking-%e6%b5%8b%e8%af%95.html" rel="bookmark" class="crp_title">Bind Variable Peeking 测试</a></li><li style="list-style-type:decimal;font-size:11px;" ><a href="https://www.xifenfei.com/2014/03/%e5%90%abis-null-sql%e8%af%ad%e5%8f%a5%e4%bc%98%e5%8c%96.html" rel="bookmark" class="crp_title">含is null sql语句优化</a></li><li style="list-style-type:decimal;font-size:11px;" ><a href="https://www.xifenfei.com/2012/06/autotrace%e6%98%be%e7%a4%bastatistics%e5%be%88%e5%a4%9a%e4%bf%a1%e6%81%af%e4%b8%ba0.html" rel="bookmark" class="crp_title">autotrace显示Statistics很多信息为0</a></li><li style="list-style-type:decimal;font-size:11px;" ><a href="https://www.xifenfei.com/2012/05/sql-profile-%e4%bd%bf%e7%94%a8.html" rel="bookmark" class="crp_title">sql profile 使用</a></li><li style="list-style-type:decimal;font-size:11px;" ><a href="https://www.xifenfei.com/2012/04/hint%e6%8c%87%e5%ae%9aindex%e7%9a%84%e6%b7%b1%e5%85%a5%e7%90%86%e8%a7%a3.html" rel="bookmark" class="crp_title">hint指定index的深入理解</a></li><li style="list-style-type:decimal;font-size:11px;" ><a href="https://www.xifenfei.com/2014/10/11g%e4%b8%ad-connect-by-%e8%af%ad%e5%8f%a5%e6%89%a7%e8%a1%8c%e8%ae%a1%e5%88%92%e6%94%b9%e5%8f%98.html" rel="bookmark" class="crp_title">11g中 connect by 语句执行计划改变</a></li><li style="list-style-type:decimal;font-size:11px;" ><a href="https://www.xifenfei.com/2011/09/oracle%e7%9b%b4%e6%96%b9%e5%9b%be%e7%90%86%e8%a7%a3%e4%b8%8e%e5%ae%9e%e9%aa%8c.html" rel="bookmark" class="crp_title">Oracle直方图理解与实验</a></li></ul></div>]]></content:encoded>
			<wfw:commentRss>https://www.xifenfei.com/2017/06/_optimizer_null_aware_antijoin-not-in.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>12.1中出现大量Result Cache: RC Latch处理</title>
		<link>https://www.xifenfei.com/2016/05/result-cache-rc-latch.html</link>
		<comments>https://www.xifenfei.com/2016/05/result-cache-rc-latch.html#comments</comments>
		<pubDate>Sun, 29 May 2016 02:23:57 +0000</pubDate>
		<dc:creator><![CDATA[惜分飞]]></dc:creator>
				<category><![CDATA[Oracle性能优化]]></category>
		<category><![CDATA[Result Cache: RC Latch]]></category>
		<category><![CDATA[_optimizer_ads_use_result_cache]]></category>

		<guid isPermaLink="false">https://www.xifenfei.com/?p=6386</guid>
		<description><![CDATA[联系：手机/微信(+86 17813235971) QQ(107644445)  &#8230; <a href="https://www.xifenfei.com/2016/05/result-cache-rc-latch.html">继续阅读 <span class="meta-nav">&#8594;</span></a>]]></description>
				<content:encoded><![CDATA[<div id="xifenfeicopyright">
<p>联系：<a href="https://www.xifenfei.com/about_xifenfei" target="_blank">手机/微信(+86 17813235971)   QQ(107644445)</a><a target="_blank" href="http://wpa.qq.com/msgrd?v=3&#038;uin=107644445&#038;site=qq&#038;menu=yes"><img src="https://www.xifenfei.com/wp-content/themes/img/site_qq.jpg" alt="QQ咨询惜分飞" title="QQ咨询惜分飞"/></a></p>
<p>标题：<a href="https://www.xifenfei.com/2016/05/result-cache-rc-latch.html" target="_blank">12.1中出现大量Result Cache: RC Latch处理</a></p>
<p>作者：<a href="https://www.xifenfei.com" target="_blank">惜分飞</a>©版权所有[未经本人同意,不得以任何形式转载,否则有进一步追究法律责任的权利.]</p>
</div>
<p>昨天有个朋友找到我说他们的12.1的库在业务高峰期非常慢，希望我们给予优化支持,经过awr分析，定位到问题为latch free问题,具体定位为:Result Cache: RC Latch.<br />
<strong>优化之前awr部分信息</strong><br />
awr整体负载情况，证明当前这个库已经比较忙，业务反馈很慢<br />
<img src="//www.xifenfei.com/wp-content/uploads/2016/05/awr1.jpg" alt="awr1" width="606" height="214" class="alignleft size-full wp-image-6392" /><br />
<hr />
addr信息和top wait信息，确定是latch free问题比较突出<br />
<img src="//www.xifenfei.com/wp-content/uploads/2016/05/awr2.jpg" alt="awr2" width="599" height="188" class="alignleft size-full wp-image-6391" /><br />
<img src="//www.xifenfei.com/wp-content/uploads/2016/05/awr3.jpg" alt="awr3" width="612" height="214" class="alignleft size-full wp-image-6390" /><br />
<hr />
latch信息统计和ash信息，找出来突出的latch,定位为Result Cache: RC Latch引起该问题<br />
<img src="//www.xifenfei.com/wp-content/uploads/2016/05/awr4.jpg" alt="awr4" width="615" height="186" class="alignleft size-full wp-image-6389" /><br />
<img src="//www.xifenfei.com/wp-content/uploads/2016/05/awr5.jpg" alt="awr5" width="790" height="206" class="alignleft size-full wp-image-6388" /><br />
<hr />
补充大量异常sql<br />
<img src="//www.xifenfei.com/wp-content/uploads/2016/05/awr6.jpg" alt="awr6" width="877" height="214" class="alignleft size-full wp-image-6387" /><br />
<hr />
类似sql语句</p>
<pre class="brush: sql; title: ; notranslate">
SELECT /* DS_SVC */ /*+ dynamic_sampling(0) no_sql_tune no_monitoring optimizer_features_enable(default) no_parallel */
 SUM(C1) FROM (SELECT /*+ qb_name(&quot;innerQuery&quot;) INDEX_FFS( &quot;ACCOUNT&quot; &quot;ACC_USER_ID&quot;) */ 
1 AS C1 FROM &quot;ACCOUNT&quot; SAMPLE BLOCK(39.3701, 8) SEED(1) &quot;ACCOUNT&quot; WHERE ( &quot;ACCOUNT&quot;.USER_ID IS NOT NULL)) innerQuery
</pre>
<p><strong>查询mos发现</strong><br />
The cause of this issue is automatic dynamic statistics which is enabled by default in 12c automatically decides whether dynamic statistics are useful and which statistics level to use for all SQL statements. It collects dynamic statistics when the optimizer deems it necessary.<br />
When Automatic Dynamic Sampling is used for the SQL statements, it can decide, based upon these statistics, that a better response time could be achieved by using the result cache for those queries. This can cause heavy usage of the result cache leading to the contention on latch free for &#8220;Result Cache: RC Latch&#8221;.<br />
也就是说,12c在自动采样有改进，而且默认使用result cache特性，从而引起该问题，即使你设置了 RESULT_CACHE_MODE = MANUAL，依旧会有大量动态采样引起 Result Cache: RC Latch，彻底解决给问题就是通过隐含参数禁止Automatic Dynamic Statistics使用result cache</p>
<pre class="brush: sql; title: ; notranslate">
alter system set &quot;_optimizer_ads_use_result_cache&quot; = FALSE;
</pre>
<p><strong>设置该参数之后效果</strong><br />
这里看，通过上述处理后，系统db time 大量减少，业务反馈已经运行正常<br />
<img src="//www.xifenfei.com/wp-content/uploads/2016/05/hawr1.jpg" alt="hawr1" width="609" height="204" class="alignleft size-full wp-image-6396" /><br />
<hr />
latch free和Result Cache: RC Latch已经基本上消失<br />
<img src="//www.xifenfei.com/wp-content/uploads/2016/05/hawr2.jpg" alt="hawr2" width="600" height="288" class="alignleft size-full wp-image-6395" /><br />
<img src="//www.xifenfei.com/wp-content/uploads/2016/05/hawr3.jpg" alt="hawr3" width="602" height="197" class="alignleft size-full wp-image-6394" /><br />
<img src="//www.xifenfei.com/wp-content/uploads/2016/05/hawr4.jpg" alt="hawr4" width="543" height="177" class="alignleft size-full wp-image-6393" /><br />
<hr />
当然这个异常是由于动态采样导致,可以通过收集数据库统计信息，设置动态采样级别，也可以从一定程度上缓解该情况.<br />
<strong>参考mos</strong><br />
Very Long Parse Time for Queries in InMemory Database (Doc ID 2102106.1)<br />
High &#8220;Latch Free&#8221; Waits with Contention on &#8216;Result Cache: RC Latch&#8217; when RESULT_CACHE_MODE = MANUAL on Oracle 12c (Doc ID 2002089.1)</p>
<div id="crp_related"><ul><li style="list-style-type:decimal;font-size:11px;" ><a href="https://www.xifenfei.com/2016/01/vmware-vsphere6-0-%e5%88%9d%e8%af%95.html" rel="bookmark" class="crp_title">VMware vSphere6.0 初试</a></li><li style="list-style-type:decimal;font-size:11px;" ><a href="https://www.xifenfei.com/2016/01/vsphere-ssh%e7%99%bb%e9%99%86%e9%85%8d%e7%bd%ae.html" rel="bookmark" class="crp_title">vSphere ssh登陆配置</a></li><li style="list-style-type:decimal;font-size:11px;" ><a href="https://www.xifenfei.com/2013/04/oracle-7-3-4-%e6%88%aa%e5%9b%be%e6%ac%a3%e8%b5%8f.html" rel="bookmark" class="crp_title">ORACLE 7.3.4 截图欣赏</a></li><li style="list-style-type:decimal;font-size:11px;" ><a href="https://www.xifenfei.com/2016/07/_offline_rollback_segments-_corrupted_rollback_segments.html" rel="bookmark" class="crp_title">_OFFLINE_ROLLBACK_SEGMENTS/_CORRUPTED_ROLLBACK_SEGMENTS</a></li><li style="list-style-type:decimal;font-size:11px;" ><a href="https://www.xifenfei.com/2026/01/hgdb-rm-rf-recovery.html" rel="bookmark" class="crp_title">记录一次国产数据库被rm -rf /*删除的救援过程</a></li><li style="list-style-type:decimal;font-size:11px;" ><a href="https://www.xifenfei.com/2018/04/enq-hw-contention.html" rel="bookmark" class="crp_title">数据文件自扩展引起&#8212;enq: HW &#8211; contention</a></li><li style="list-style-type:decimal;font-size:11px;" ><a href="https://www.xifenfei.com/2015/11/windows-listener-log-4g.html" rel="bookmark" class="crp_title">windows平台listener.log超过4G导致监听异常</a></li><li style="list-style-type:decimal;font-size:11px;" ><a href="https://www.xifenfei.com/2015/04/%e9%80%9a%e8%bf%87administration-assistant-for-windows%e9%85%8d%e7%bd%aewin%e6%9c%8d%e5%8a%a1%e5%92%8c%e5%ae%9e%e4%be%8b%e5%85%b3%e8%81%94%e6%80%a7.html" rel="bookmark" class="crp_title">通过Administration Assistant for Windows配置win服务和实例关联性</a></li><li style="list-style-type:decimal;font-size:11px;" ><a href="https://www.xifenfei.com/2012/07/%e9%80%9a%e8%bf%87awr%e6%8c%87%e6%a0%87%e8%af%84%e4%bc%b0%e4%bc%9a%e8%af%9d%e5%bb%ba%e7%ab%8b%e6%98%af%e5%90%a6%e9%a2%91%e7%b9%81.html" rel="bookmark" class="crp_title">通过awr指标评估会话建立是否频繁</a></li><li style="list-style-type:decimal;font-size:11px;" ><a href="https://www.xifenfei.com/2025/12/sql-bak-0-lost-data.html" rel="bookmark" class="crp_title">模拟sql server故障备份完成恢复实现数据0丢失</a></li><li style="list-style-type:decimal;font-size:11px;" ><a href="https://www.xifenfei.com/2025/12/ufs-recovery-lvm.html" rel="bookmark" class="crp_title">linux异常磁盘lvm恢复操作演示</a></li><li style="list-style-type:decimal;font-size:11px;" ><a href="https://www.xifenfei.com/2025/10/linux7-8-single-user.html" rel="bookmark" class="crp_title">redhat系列7/8进入单用户模式</a></li></ul></div>]]></content:encoded>
			<wfw:commentRss>https://www.xifenfei.com/2016/05/result-cache-rc-latch.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>sql profile改变hint的执行计划以及coe脚本实现sql id中无PLAN HASH VALUE的sql profile生成</title>
		<link>https://www.xifenfei.com/2015/06/sql-profile%e6%94%b9%e5%8f%98hint%e7%9a%84%e6%89%a7%e8%a1%8c%e8%ae%a1%e5%88%92%e4%bb%a5%e5%8f%8acoe%e8%84%9a%e6%9c%ac%e5%ae%9e%e7%8e%b0sql-id%e4%b8%ad%e6%97%a0plan-hash-value%e7%9a%84sql-profile.html</link>
		<comments>https://www.xifenfei.com/2015/06/sql-profile%e6%94%b9%e5%8f%98hint%e7%9a%84%e6%89%a7%e8%a1%8c%e8%ae%a1%e5%88%92%e4%bb%a5%e5%8f%8acoe%e8%84%9a%e6%9c%ac%e5%ae%9e%e7%8e%b0sql-id%e4%b8%ad%e6%97%a0plan-hash-value%e7%9a%84sql-profile.html#comments</comments>
		<pubDate>Sun, 31 May 2015 17:01:05 +0000</pubDate>
		<dc:creator><![CDATA[惜分飞]]></dc:creator>
				<category><![CDATA[Oracle性能优化]]></category>
		<category><![CDATA[coe_load_sql_profile]]></category>
		<category><![CDATA[coe_xfr_sql_profile]]></category>
		<category><![CDATA[hint]]></category>
		<category><![CDATA[sql profile]]></category>

		<guid isPermaLink="false">https://www.xifenfei.com/?p=5915</guid>
		<description><![CDATA[联系：手机/微信(+86 17813235971) QQ(107644445)  &#8230; <a href="https://www.xifenfei.com/2015/06/sql-profile%e6%94%b9%e5%8f%98hint%e7%9a%84%e6%89%a7%e8%a1%8c%e8%ae%a1%e5%88%92%e4%bb%a5%e5%8f%8acoe%e8%84%9a%e6%9c%ac%e5%ae%9e%e7%8e%b0sql-id%e4%b8%ad%e6%97%a0plan-hash-value%e7%9a%84sql-profile.html">继续阅读 <span class="meta-nav">&#8594;</span></a>]]></description>
				<content:encoded><![CDATA[<div id="xifenfeicopyright">
<p>联系：<a href="https://www.xifenfei.com/about_xifenfei" target="_blank">手机/微信(+86 17813235971)   QQ(107644445)</a><a target="_blank" href="http://wpa.qq.com/msgrd?v=3&#038;uin=107644445&#038;site=qq&#038;menu=yes"><img src="https://www.xifenfei.com/wp-content/themes/img/site_qq.jpg" alt="QQ咨询惜分飞" title="QQ咨询惜分飞"/></a></p>
<p>标题：<a href="https://www.xifenfei.com/2015/06/sql-profile%e6%94%b9%e5%8f%98hint%e7%9a%84%e6%89%a7%e8%a1%8c%e8%ae%a1%e5%88%92%e4%bb%a5%e5%8f%8acoe%e8%84%9a%e6%9c%ac%e5%ae%9e%e7%8e%b0sql-id%e4%b8%ad%e6%97%a0plan-hash-value%e7%9a%84sql-profile.html" target="_blank">sql profile改变hint的执行计划以及coe脚本实现sql id中无PLAN HASH VALUE的sql profile生成</a></p>
<p>作者：<a href="https://www.xifenfei.com" target="_blank">惜分飞</a>©版权所有[未经本人同意,不得以任何形式转载,否则有进一步追究法律责任的权利.]</p>
</div>
<p>在sql profile中使用的过程中,有以下几个问题,这里通过测试确认了几个问题:<br />
1.coe_xfr_sql_profile可以执行sql_id中无PLAN HASH VALUE的执行计划<br />
2.在sql使用过程中,sql profile是否会覆盖hint,通过测试证明sqlprofile可以覆盖hint的执行计划<br />
3.coe_load_sql_profile可以使用于通过修改hint(改变sql id,然后通过指定两次不同的sql id实现sql profile固定hint的sql的执行计划)<br />
<br />
<strong>测试sqlprofile会影响hint</strong></p>
<pre class="brush: sql; title: ; notranslate">
SQL&gt; create table t_xifenfei as select object_id,object_name from user_objects;

Table created.

SQL&gt; create index idx_t_xifenfei_id on t_xifenfei(OBJECT_ID);

Index created.

SQL&gt; create index idx_t_xifenfei2_id on t_xifenfei(OBJECT_ID,1);

Index created.

---使用hint等方式确定三种方式执行计划
SQL&gt; SET LINES 150
SQL&gt; SET AUTOT  ON
SQL&gt; SET PAGES 150
SQL&gt; select * from t_xifenfei t where OBJECT_ID=10;    &lt;---默认使用IDX_T_XIFENFEI_ID index

no rows selected


Execution Plan
----------------------------------------------------------
Plan hash value: 308895000

-------------------------------------------------------------------------------------------------
| Id  | Operation                   | Name              | Rows  | Bytes | Cost (%CPU)| Time     |
-------------------------------------------------------------------------------------------------
|   0 | SELECT STATEMENT            |                   |     1 |    79 |     1   (0)| 00:00:01 |
|   1 |  TABLE ACCESS BY INDEX ROWID| T_XIFENFEI        |     1 |    79 |     1   (0)| 00:00:01 |
|*  2 |   INDEX RANGE SCAN          | IDX_T_XIFENFEI_ID |     1 |       |     1   (0)| 00:00:01 |
-------------------------------------------------------------------------------------------------

Predicate Information (identified by operation id):
---------------------------------------------------

   2 - access(&quot;OBJECT_ID&quot;=10)

Note
-----
   - dynamic sampling used for this statement (level=2)


Statistics
----------------------------------------------------------
          6  recursive calls
          0  db block gets
         13  consistent gets
          1  physical reads
          0  redo size
        410  bytes sent via SQL*Net to client
        513  bytes received via SQL*Net from client
          1  SQL*Net roundtrips to/from client
          0  sorts (memory)
          0  sorts (disk)
          0  rows processed

SQL&gt; SET AUTOT OFF

SQL&gt; SET LINES 150
SQL&gt; SET AUTOT  ON
SQL&gt; SET PAGES 150
SQL&gt; select /*+ INDEX(T idx_t_xifenfei2_id)*/* from t_xifenfei t where OBJECT_ID=10;
  &lt;---指定使用idx_t_xifenfei2_id index

no rows selected


Execution Plan
----------------------------------------------------------
Plan hash value: 2143066642

--------------------------------------------------------------------------------------------------
| Id  | Operation                   | Name               | Rows  | Bytes | Cost (%CPU)| Time     |
--------------------------------------------------------------------------------------------------
|   0 | SELECT STATEMENT            |                    |     1 |    79 |     1   (0)| 00:00:01 |
|   1 |  TABLE ACCESS BY INDEX ROWID| T_XIFENFEI         |     1 |    79 |     1   (0)| 00:00:01 |
|*  2 |   INDEX RANGE SCAN          | IDX_T_XIFENFEI2_ID |     1 |       |     1   (0)| 00:00:01 |
--------------------------------------------------------------------------------------------------

Predicate Information (identified by operation id):
---------------------------------------------------

   2 - access(&quot;OBJECT_ID&quot;=10)

Note
-----
   - dynamic sampling used for this statement (level=2)


Statistics
----------------------------------------------------------
          4  recursive calls
          0  db block gets
         11  consistent gets
          1  physical reads
          0  redo size
        410  bytes sent via SQL*Net to client
        513  bytes received via SQL*Net from client
          1  SQL*Net roundtrips to/from client
          0  sorts (memory)
          0  sorts (disk)
          0  rows processed

SQL&gt; SET AUTOT OFF

SQL&gt; SET LINES 150
SQL&gt; SET AUTOT  ON
SQL&gt; SET PAGES 150
SQL&gt; select /*+ INDEX(T idx_t_xifenfei_id)*/* from t_xifenfei t where OBJECT_ID=10;
  &lt;---指定使用idx_t_xifenfei1_id index

no rows selected


Execution Plan
----------------------------------------------------------
Plan hash value: 308895000

-------------------------------------------------------------------------------------------------
| Id  | Operation                   | Name              | Rows  | Bytes | Cost (%CPU)| Time     |
-------------------------------------------------------------------------------------------------
|   0 | SELECT STATEMENT            |                   |     1 |    79 |     1   (0)| 00:00:01 |
|   1 |  TABLE ACCESS BY INDEX ROWID| T_XIFENFEI        |     1 |    79 |     1   (0)| 00:00:01 |
|*  2 |   INDEX RANGE SCAN          | IDX_T_XIFENFEI_ID |     1 |       |     1   (0)| 00:00:01 |
-------------------------------------------------------------------------------------------------

Predicate Information (identified by operation id):
---------------------------------------------------

   2 - access(&quot;OBJECT_ID&quot;=10)

Note
-----
   - dynamic sampling used for this statement (level=2)


Statistics
----------------------------------------------------------
          4  recursive calls
          0  db block gets
         11  consistent gets
          0  physical reads
          0  redo size
        410  bytes sent via SQL*Net to client
        513  bytes received via SQL*Net from client
          1  SQL*Net roundtrips to/from client
          0  sorts (memory)
          0  sorts (disk)
          0  rows processed

SQL&gt; SET AUTOT OFF

--查询三种情况下sql_id
SQL&gt; col SQL_TEXT for a50
SQL&gt; SELECT SQL_TEXT,SQL_ID FROM V$SQL WHERE sql_text like 'select%OBJECT_ID=10';

SQL_TEXT                                           SQL_ID
-------------------------------------------------- -------------
select /*+ INDEX(T idx_t_xifenfei2_id)*/* from t_x 5291sfrd2p35y
ifenfei t where OBJECT_ID=10

select /*+ INDEX(T idx_t_xifenfei_id)*/* from t_xi 143q33ff4f06w
fenfei t where OBJECT_ID=10

select * from t_xifenfei t where OBJECT_ID=10      b5zuac0zqm9nw

--使用sqlprofile固定其他两个未使用index IDX_T_XIFENFEI2_ID的sql使用该索引
SQL&gt; DECLARE
  2   SQL_FTEXT CLOB;
  3   BEGIN
  4   SELECT SQL_FULLTEXT INTO SQL_FTEXT FROM V$SQLAREA WHERE SQL_ID = 'b5zuac0zqm9nw';
  5   DBMS_SQLTUNE.IMPORT_SQL_PROFILE(
  6     SQL_TEXT =&gt; SQL_FTEXT,
  7     PROFILE =&gt; SQLPROF_ATTR('INDEX(@&quot;SEL$1&quot; &quot;T&quot;@&quot;SEL$1&quot; &quot;IDX_T_XIFENFEI2_ID&quot;)'),
  8     NAME =&gt; 'PROFILE_b5zuac0zqm9nw',
  9     REPLACE =&gt; TRUE,
  10    FORCE_MATCH =&gt; TRUE
  11  );
 12   END;
 13   /

PL/SQL procedure successfully completed.

SQL&gt; 
SQL&gt; DECLARE
  2    SQL_FTEXT CLOB;
  3   BEGIN
  4   SELECT SQL_FULLTEXT INTO SQL_FTEXT FROM V$SQLAREA WHERE SQL_ID = '143q33ff4f06w';
  5   DBMS_SQLTUNE.IMPORT_SQL_PROFILE(
  6     SQL_TEXT =&gt; SQL_FTEXT,
  7     PROFILE =&gt; SQLPROF_ATTR('INDEX(@&quot;SEL$1&quot; &quot;T&quot;@&quot;SEL$1&quot; &quot;IDX_T_XIFENFEI2_ID&quot;)'),
  8      NAME =&gt; 'PROFILE_143q33ff4f06w',
  9     REPLACE =&gt; TRUE,
 10     FORCE_MATCH =&gt; TRUE
 11   );
 12   END;
13   / 

PL/SQL procedure successfully completed.

--验证查询效果
SQL&gt; SET LINES 150
SQL&gt; SET AUTOT  ON
SQL&gt; SET PAGES 150
SQL&gt; select * from t_xifenfei t where OBJECT_ID=10;

no rows selected


Execution Plan
----------------------------------------------------------
Plan hash value: 2143066642

--------------------------------------------------------------------------------------------------
| Id  | Operation                   | Name               | Rows  | Bytes | Cost (%CPU)| Time     |
--------------------------------------------------------------------------------------------------
|   0 | SELECT STATEMENT            |                    |     1 |    79 |     1   (0)| 00:00:01 |
|   1 |  TABLE ACCESS BY INDEX ROWID| T_XIFENFEI         |     1 |    79 |     1   (0)| 00:00:01 |
|*  2 |   INDEX RANGE SCAN          | IDX_T_XIFENFEI2_ID |     1 |       |     1   (0)| 00:00:01 |
--------------------------------------------------------------------------------------------------

Predicate Information (identified by operation id):
---------------------------------------------------

   2 - access(&quot;OBJECT_ID&quot;=10)

Note
-----
   - dynamic sampling used for this statement (level=2)
   - SQL profile &quot;PROFILE_b5zuac0zqm9nw&quot; used for this statement  &lt;--使用sql profile


Statistics
----------------------------------------------------------
         37  recursive calls
          0  db block gets
         23  consistent gets
          1  physical reads
          0  redo size
        410  bytes sent via SQL*Net to client
        513  bytes received via SQL*Net from client
          1  SQL*Net roundtrips to/from client
          1  sorts (memory)
          0  sorts (disk)
          0  rows processed

SQL&gt; select /*+ INDEX(T idx_t_xifenfei_id)*/* from t_xifenfei t where OBJECT_ID=10;

no rows selected


Execution Plan
----------------------------------------------------------
Plan hash value: 2143066642

--------------------------------------------------------------------------------------------------
| Id  | Operation                   | Name               | Rows  | Bytes | Cost (%CPU)| Time     |
--------------------------------------------------------------------------------------------------
|   0 | SELECT STATEMENT            |                    |     1 |    79 |     1   (0)| 00:00:01 |
|   1 |  TABLE ACCESS BY INDEX ROWID| T_XIFENFEI         |     1 |    79 |     1   (0)| 00:00:01 |
|*  2 |   INDEX RANGE SCAN          | IDX_T_XIFENFEI2_ID |     1 |       |     1   (0)| 00:00:01 |
--------------------------------------------------------------------------------------------------

Predicate Information (identified by operation id):
---------------------------------------------------

   2 - access(&quot;OBJECT_ID&quot;=10)

Note
-----
   - dynamic sampling used for this statement (level=2)
   - SQL profile &quot;PROFILE_143q33ff4f06w&quot; used for this statement 

&lt;--使用sql profile,hint未被正常使用，证明sql profile影响hint，使得sql使用sql profile而不hint


Statistics
----------------------------------------------------------
         10  recursive calls
          0  db block gets
         16  consistent gets
          1  physical reads
          0  redo size
        410  bytes sent via SQL*Net to client
        513  bytes received via SQL*Net from client
          1  SQL*Net roundtrips to/from client
          0  sorts (memory)
          0  sorts (disk)
          0  rows processed
</pre>
<p>这里可以知道,在有sqlprofile的情况下,可以影响以前的hint提示,使得hint无效，继续使用sql profile,感谢北京&#8211;weejar的试验证明<br />
<br />
<strong>使用coe_load_sql_profile方式指定修改sql后的执行计划</strong></p>
<pre class="brush: sql; title: ; notranslate">
SQL&gt; @/tmp/coe_load_sql_profile.sql

Parameter 1:
ORIGINAL_SQL_ID (required)

Enter value for 1: b5zuac0zqm9nw

Parameter 2:
MODIFIED_SQL_ID (required)

Enter value for 2: 5291sfrd2p35y


     PLAN_HASH_VALUE          AVG_ET_SECS
-------------------- --------------------
          2143066642                 .004

Parameter 3:
PLAN_HASH_VALUE (required)

Enter value for 3: 2143066642

Values passed to coe_load_sql_profile:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
ORIGINAL_SQL_ID: &quot;b5zuac0zqm9nw&quot;
MODIFIED_SQL_ID: &quot;5291sfrd2p35y&quot;
PLAN_HASH_VALUE: &quot;2143066642&quot;

SQL&gt;BEGIN
  2    IF :sql_text IS NULL THEN
  3      RAISE_APPLICATION_ERROR(-20100, 'SQL_TEXT for original SQL_ID &amp;&amp;original_sql_id.
       was not found in memory (gv$sqltext_with_newlines) or AWR (dba_hist_sqltext).');
  4    END IF;
  5  END;
  6  /
SQL&gt;SET TERM OFF;
SQL&gt;BEGIN
  2    IF :other_xml IS NULL THEN
  3      RAISE_APPLICATION_ERROR(-20101, 'PLAN for modified SQL_ID &amp;&amp;modified_sql_id. and PHV &amp;&amp;plan_hash_value.
         was not found in memory (gv$sql_plan) or AWR (dba_hist_sql_plan).');
  4    END IF;
  5  END;
  6  /
SQL&gt;
SQL&gt;SET ECHO OFF;
0001 BEGIN_OUTLINE_DATA
0002 IGNORE_OPTIM_EMBEDDED_HINTS
0003 OPTIMIZER_FEATURES_ENABLE('11.2.0.4')
0004 DB_VERSION('11.2.0.4')
0005 ALL_ROWS
0006 OUTLINE_LEAF(@&quot;SEL$1&quot;)
0007 INDEX_RS_ASC(@&quot;SEL$1&quot; &quot;T&quot;@&quot;SEL$1&quot; &quot;IDX_T_XIFENFEI2_ID&quot;)
0008 END_OUTLINE_DATA
dropping staging table &quot;STGTAB_SQLPROF_B5ZUAC0ZQM9NW&quot;
creating staging table &quot;STGTAB_SQLPROF_B5ZUAC0ZQM9NW&quot;
packaging new sql profile into staging table &quot;STGTAB_SQLPROF_B5ZUAC0ZQM9NW&quot;

PROFILE_NAME
------------------------------
B5ZUAC0ZQM9NW_2143066642
SQL&gt;REM
SQL&gt;REM SQL Profile
SQL&gt;REM ~~~~~~~~~~~
SQL&gt;REM
SQL&gt;SELECT signature, name, category, type, status
  2    FROM dba_sql_profiles WHERE name = :name;

           SIGNATURE NAME                           CATEGORY                       TYPE    STATUS
-------------------- ------------------------------ ------------------------------ ------- --------
 6715790053022671751 B5ZUAC0ZQM9NW_2143066642       DEFAULT                        MANUAL  ENABLED
SQL&gt;SET ECHO OFF;

****************************************************************************
* Enter CHF password to export staging table STGTAB_SQLPROF_b5zuac0zqm9nw
****************************************************************************

Export: Release 11.2.0.4.0 - Production on Mon Jun 1 00:10:11 2015

Copyright (c) 1982, 2011, Oracle and/or its affiliates.  All rights reserved.

Password: 

Connected to: Oracle Database 11g Enterprise Edition Release 11.2.0.4.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
Export done in US7ASCII character set and AL16UTF16 NCHAR character set
server uses ZHS16GBK character set (possible charset conversion)
Note: grants on tables/views/sequences/roles will not be exported
Note: indexes on tables will not be exported
Note: constraints on tables will not be exported

About to export specified tables via Conventional Path ...
. . exporting table   STGTAB_SQLPROF_B5ZUAC0ZQM9NW          1 rows exported
Export terminated successfully without warnings.


If you need to implement this Custom SQL Profile on a similar system,
import and unpack using these commands:

imp CHF file=STGTAB_SQLPROF_b5zuac0zqm9nw.dmp tables=STGTAB_SQLPROF_b5zuac0zqm9nw ignore=Y

BEGIN
DBMS_SQLTUNE.UNPACK_STGTAB_SQLPROF (
profile_name =&gt; 'B5ZUAC0ZQM9NW_2143066642',
replace =&gt; TRUE,
staging_table_name =&gt; 'STGTAB_SQLPROF_b5zuac0zqm9nw',
staging_schema_owner =&gt; 'CHF' );
END;
/

updating: coe_load_sql_profile_b5zuac0zqm9nw.log (deflated 76%)
updating: STGTAB_SQLPROF_b5zuac0zqm9nw.dmp (deflated 89%)
  adding: coe_load_sql_profile.log (deflated 62%)

deleting: coe_load_sql_profile.log


coe_load_sql_profile completed.

SQL&gt;SET LINES 150
SQL&gt;SET AUTOT  ON
SQL&gt;SET PAGES 150
select * from t_xifenfei t where OBJECT_ID=10;SQL&gt;

no rows selected


Execution Plan
----------------------------------------------------------
Plan hash value: 2143066642

--------------------------------------------------------------------------------------------------
| Id  | Operation                   | Name               | Rows  | Bytes | Cost (%CPU)| Time     |
--------------------------------------------------------------------------------------------------
|   0 | SELECT STATEMENT            |                    |     6 |   474 |     3   (0)| 00:00:01 |
|   1 |  TABLE ACCESS BY INDEX ROWID| T_XIFENFEI         |     6 |   474 |     3   (0)| 00:00:01 |
|*  2 |   INDEX RANGE SCAN          | IDX_T_XIFENFEI2_ID |     2 |       |     2   (0)| 00:00:01 |
--------------------------------------------------------------------------------------------------

Predicate Information (identified by operation id):
---------------------------------------------------

   2 - access(&quot;OBJECT_ID&quot;=10)

Note
-----
   - SQL profile &quot;B5ZUAC0ZQM9NW_2143066642&quot; used for this statement   
&lt;------sql直接使用coe_load_sql_profile固定执行计划成功


Statistics
----------------------------------------------------------
          7  recursive calls
          0  db block gets
          7  consistent gets
          1  physical reads
          0  redo size
        410  bytes sent via SQL*Net to client
        513  bytes received via SQL*Net from client
          1  SQL*Net roundtrips to/from client
          0  sorts (memory)
          0  sorts (disk)
          0  rows processed
</pre>
<p>使用coe_load_sql_profile也可以sql_id中没有PLAN HASH VALUE的执行计划,另外还可以实现直接把sqlprofile直接迁移到其他库中<br />
<br />
<strong>coe_xfr_sql_profile固定没有sql_id没有直接PLAN HASH VALUE的执行计划</strong></p>
<pre class="brush: sql; title: ; notranslate">
SQL&gt; @/tmp/coe_xfr_sql_profile

Parameter 1:
SQL_ID (required)

Enter value for 1: b5zuac0zqm9nw


PLAN_HASH_VALUE AVG_ET_SECS
--------------- -----------
      308895000        .005

Parameter 2:
PLAN_HASH_VALUE (required)

Enter value for 2: 2143066642     &lt;---该PLAN_HASH_VALUE不存在该sql_id对应的PLAN_HASH_VALUE中

Values passed to coe_xfr_sql_profile:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
SQL_ID         : &quot;b5zuac0zqm9nw&quot;
PLAN_HASH_VALUE: &quot;2143066642&quot;

SQL&gt;BEGIN
  2    IF :sql_text IS NULL THEN
  3      RAISE_APPLICATION_ERROR(-20100, 'SQL_TEXT for SQL_ID &amp;&amp;sql_id. was not 
      found in memory (gv$sqltext_with_newlines) or AWR (dba_hist_sqltext).');
  4    END IF;
  5  END;
  6  /
SQL&gt;SET TERM OFF;
SQL&gt;BEGIN
  2    IF :other_xml IS NULL THEN
  3      RAISE_APPLICATION_ERROR(-20101, 'PLAN for SQL_ID &amp;&amp;sql_id. and PHV &amp;&amp;plan_hash_value.
      was not found in memory (gv$sql_plan) or AWR (dba_hist_sql_plan).');
  4    END IF;
  5  END;
  6  /
SQL&gt;SET TERM OFF;

Execute coe_xfr_sql_profile_b5zuac0zqm9nw_2143066642.sql
on TARGET system in order to create a custom SQL Profile
with plan 2143066642 linked to adjusted sql_text.


COE_XFR_SQL_PROFILE completed.
SQL&gt;@coe_xfr_sql_profile_b5zuac0zqm9nw_2143066642.sql
SQL&gt;REM
SQL&gt;REM $Header: 215187.1 coe_xfr_sql_profile_b5zuac0zqm9nw_2143066642.sql 11.4.4.4 2015/06/01 carlos.sierra $
SQL&gt;REM
SQL&gt;REM Copyright (c) 2000-2012, Oracle Corporation. All rights reserved.
SQL&gt;REM
SQL&gt;REM AUTHOR
SQL&gt;REM   carlos.sierra@oracle.com
SQL&gt;REM
SQL&gt;REM SCRIPT
SQL&gt;REM   coe_xfr_sql_profile_b5zuac0zqm9nw_2143066642.sql
SQL&gt;REM
SQL&gt;REM DESCRIPTION
SQL&gt;REM   This script is generated by coe_xfr_sql_profile.sql
SQL&gt;REM   It contains the SQL*Plus commands to create a custom
SQL&gt;REM   SQL Profile for SQL_ID b5zuac0zqm9nw based on plan hash
SQL&gt;REM   value 2143066642.
SQL&gt;REM   The custom SQL Profile to be created by this script
SQL&gt;REM   will affect plans for SQL commands with signature
SQL&gt;REM   matching the one for SQL Text below.
SQL&gt;REM   Review SQL Text and adjust accordingly.
SQL&gt;REM
SQL&gt;REM PARAMETERS
SQL&gt;REM   None.
SQL&gt;REM
SQL&gt;REM EXAMPLE
SQL&gt;REM   SQL&gt; START coe_xfr_sql_profile_b5zuac0zqm9nw_2143066642.sql;
SQL&gt;REM
SQL&gt;REM NOTES
SQL&gt;REM   1. Should be run as SYSTEM or SYSDBA.
SQL&gt;REM   2. User must have CREATE ANY SQL PROFILE privilege.
SQL&gt;REM   3. SOURCE and TARGET systems can be the same or similar.
SQL&gt;REM   4. To drop this custom SQL Profile after it has been created:
SQL&gt;REM  EXEC DBMS_SQLTUNE.DROP_SQL_PROFILE('coe_b5zuac0zqm9nw_2143066642');
SQL&gt;REM   5. Be aware that using DBMS_SQLTUNE requires a license
SQL&gt;REM  for the Oracle Tuning Pack.
SQL&gt;REM   6. If you modified a SQL putting Hints in order to produce a desired
SQL&gt;REM  Plan, you can remove the artifical Hints from SQL Text pieces below.
SQL&gt;REM  By doing so you can create a custom SQL Profile for the original
SQL&gt;REM  SQL but with the Plan captured from the modified SQL (with Hints).
SQL&gt;REM
SQL&gt;WHENEVER SQLERROR EXIT SQL.SQLCODE;
SQL&gt;REM
SQL&gt;VAR signature NUMBER;
SQL&gt;VAR signaturef NUMBER;
SQL&gt;REM
SQL&gt;DECLARE
  2  sql_txt CLOB;
  3  h       SYS.SQLPROF_ATTR;
  4  PROCEDURE wa (p_line IN VARCHAR2) IS
  5  BEGIN
  6  DBMS_LOB.WRITEAPPEND(sql_txt, LENGTH(p_line), p_line);
  7  END wa;
  8  BEGIN
  9  DBMS_LOB.CREATETEMPORARY(sql_txt, TRUE);
 10  DBMS_LOB.OPEN(sql_txt, DBMS_LOB.LOB_READWRITE);
 11  -- SQL Text pieces below do not have to be of same length.
 12  -- So if you edit SQL Text (i.e. removing temporary Hints),
 13  -- there is no need to edit or re-align unmodified pieces.
 14  wa(q'[select * from t_xifenfei t where OBJECT_ID=10]');
 15  DBMS_LOB.CLOSE(sql_txt);
 16  h := SYS.SQLPROF_ATTR(
 17  q'[BEGIN_OUTLINE_DATA]',
 18  q'[IGNORE_OPTIM_EMBEDDED_HINTS]',
 19  q'[OPTIMIZER_FEATURES_ENABLE('11.2.0.4')]',
 20  q'[DB_VERSION('11.2.0.4')]',
 21  q'[ALL_ROWS]',
 22  q'[OUTLINE_LEAF(@&quot;SEL$1&quot;)]',
 23  q'[INDEX_RS_ASC(@&quot;SEL$1&quot; &quot;T&quot;@&quot;SEL$1&quot; &quot;IDX_T_XIFENFEI2_ID&quot;)]',
 24  q'[END_OUTLINE_DATA]');
 25  :signature := DBMS_SQLTUNE.SQLTEXT_TO_SIGNATURE(sql_txt);
 26  :signaturef := DBMS_SQLTUNE.SQLTEXT_TO_SIGNATURE(sql_txt, TRUE);
 27  DBMS_SQLTUNE.IMPORT_SQL_PROFILE (
 28  sql_text    =&gt; sql_txt,
 29  profile     =&gt; h,
 30  name        =&gt; 'coe_b5zuac0zqm9nw_2143066642',
 31  description =&gt; 'coe b5zuac0zqm9nw 2143066642 '||:signature||' '||:signaturef||'',
 32  category    =&gt; 'DEFAULT',
 33  validate    =&gt; TRUE,
 34  replace     =&gt; TRUE,
 35  force_match =&gt; FALSE /* TRUE:FORCE (match even when different literals in SQL). 
     FALSE:EXACT (similar to CURSOR_SHARING) */ );
 36  DBMS_LOB.FREETEMPORARY(sql_txt);
 37  END;
 38  /

PL/SQL procedure successfully completed.

SQL&gt;WHENEVER SQLERROR CONTINUE
SQL&gt;SET ECHO OFF;

            SIGNATURE
---------------------
  6715790053022671751


           SIGNATUREF
---------------------
   445801536248906164


... manual custom SQL Profile has been created


COE_XFR_SQL_PROFILE_b5zuac0zqm9nw_2143066642 completed
SQL&gt;set autot on
SQL&gt;set lines 150
SQL&gt;set pages 150
SQL&gt;select * from t_xifenfei t where OBJECT_ID=10;

no rows selected


Execution Plan
----------------------------------------------------------
Plan hash value: 2143066642

--------------------------------------------------------------------------------------------------
| Id  | Operation                   | Name               | Rows  | Bytes | Cost (%CPU)| Time     |
--------------------------------------------------------------------------------------------------
|   0 | SELECT STATEMENT            |                    |     6 |   474 |     3   (0)| 00:00:01 |
|   1 |  TABLE ACCESS BY INDEX ROWID| T_XIFENFEI         |     6 |   474 |     3   (0)| 00:00:01 |
|*  2 |   INDEX RANGE SCAN          | IDX_T_XIFENFEI2_ID |     2 |       |     2   (0)| 00:00:01 |
--------------------------------------------------------------------------------------------------

Predicate Information (identified by operation id):
---------------------------------------------------

   2 - access(&quot;OBJECT_ID&quot;=10)

Note
-----
   - SQL profile &quot;coe_b5zuac0zqm9nw_2143066642&quot; used for this statement


Statistics
----------------------------------------------------------
          7  recursive calls
          0  db block gets
          7  consistent gets
          1  physical reads
          0  redo size
        410  bytes sent via SQL*Net to client
        513  bytes received via SQL*Net from client
          1  SQL*Net roundtrips to/from client
          0  sorts (memory)
          0  sorts (disk)
          0  rows processed

SQL&gt;
</pre>
<p>通过验证，证明在sql_id中没有对应的PLAN HASH VALUE之时，也可以通过coe_xfr_sql_profile指定PLAN HASH VALUE来固定某个sql_id的执行计划.<br />
以前写过相关关于sql profile的文章:<a href="//www.xifenfei.com/3044.html" title="sql profile 使用" target="_blank">sql profile 使用</a>,<a href="//www.xifenfei.com/5309.html" title="执行计划改变导致数据库负载过高" target="_blank">执行计划改变导致数据库负载过高</a></p>
<div id="crp_related"><ul><li style="list-style-type:decimal;font-size:11px;" ><a href="https://www.xifenfei.com/2012/05/sql-profile-%e4%bd%bf%e7%94%a8.html" rel="bookmark" class="crp_title">sql profile 使用</a></li><li style="list-style-type:decimal;font-size:11px;" ><a href="https://www.xifenfei.com/2012/04/%e6%89%a7%e8%a1%8c%e8%ae%a1%e5%88%92%e4%b8%ad%e5%b8%b8%e8%a7%81index%e8%ae%bf%e9%97%ae%e6%96%b9%e5%bc%8f.html" rel="bookmark" class="crp_title">执行计划中常见index访问方式</a></li><li style="list-style-type:decimal;font-size:11px;" ><a href="https://www.xifenfei.com/2012/12/%e5%88%9b%e5%bb%ba%e6%94%af%e6%8c%81null-index.html" rel="bookmark" class="crp_title">创建包含null值index</a></li><li style="list-style-type:decimal;font-size:11px;" ><a href="https://www.xifenfei.com/2011/07/select-maxamina-from-table%e4%bc%98%e5%8c%96.html" rel="bookmark" class="crp_title">select max(id),min(id) from table优化</a></li><li style="list-style-type:decimal;font-size:11px;" ><a href="https://www.xifenfei.com/2019/04/sql-plan-baseline.html" rel="bookmark" class="crp_title">sql plan baseline简单介绍</a></li><li style="list-style-type:decimal;font-size:11px;" ><a href="https://www.xifenfei.com/2012/04/hint%e6%8c%87%e5%ae%9aindex%e7%9a%84%e6%b7%b1%e5%85%a5%e7%90%86%e8%a7%a3.html" rel="bookmark" class="crp_title">hint指定index的深入理解</a></li><li style="list-style-type:decimal;font-size:11px;" ><a href="https://www.xifenfei.com/2017/06/_optimizer_null_aware_antijoin-not-in.html" rel="bookmark" class="crp_title">_optimizer_null_aware_antijoin和not in效率</a></li><li style="list-style-type:decimal;font-size:11px;" ><a href="https://www.xifenfei.com/2014/03/%e5%90%abis-null-sql%e8%af%ad%e5%8f%a5%e4%bc%98%e5%8c%96.html" rel="bookmark" class="crp_title">含is null sql语句优化</a></li><li style="list-style-type:decimal;font-size:11px;" ><a href="https://www.xifenfei.com/2014/10/11g%e4%b8%ad-connect-by-%e8%af%ad%e5%8f%a5%e6%89%a7%e8%a1%8c%e8%ae%a1%e5%88%92%e6%94%b9%e5%8f%98.html" rel="bookmark" class="crp_title">11g中 connect by 语句执行计划改变</a></li><li style="list-style-type:decimal;font-size:11px;" ><a href="https://www.xifenfei.com/2012/05/bind-variable-peeking-%e6%b5%8b%e8%af%95.html" rel="bookmark" class="crp_title">Bind Variable Peeking 测试</a></li><li style="list-style-type:decimal;font-size:11px;" ><a href="https://www.xifenfei.com/2013/04/12c-top-n-sql%e5%ae%9e%e7%8e%b0%e5%88%86%e9%a1%b5%e5%8a%9f%e8%83%bd.html" rel="bookmark" class="crp_title">ORACLE 12C TOP N SQL实现分页功能</a></li><li style="list-style-type:decimal;font-size:11px;" ><a href="https://www.xifenfei.com/2011/09/oracle%e7%9b%b4%e6%96%b9%e5%9b%be%e7%90%86%e8%a7%a3%e4%b8%8e%e5%ae%9e%e9%aa%8c.html" rel="bookmark" class="crp_title">Oracle直方图理解与实验</a></li></ul></div>]]></content:encoded>
			<wfw:commentRss>https://www.xifenfei.com/2015/06/sql-profile%e6%94%b9%e5%8f%98hint%e7%9a%84%e6%89%a7%e8%a1%8c%e8%ae%a1%e5%88%92%e4%bb%a5%e5%8f%8acoe%e8%84%9a%e6%9c%ac%e5%ae%9e%e7%8e%b0sql-id%e4%b8%ad%e6%97%a0plan-hash-value%e7%9a%84sql-profile.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Oracle 12C TABLE ACCESS BY INDEX ROWID BATCHED</title>
		<link>https://www.xifenfei.com/2015/05/oracle-12c-table-access-by-index-rowid-batched.html</link>
		<comments>https://www.xifenfei.com/2015/05/oracle-12c-table-access-by-index-rowid-batched.html#comments</comments>
		<pubDate>Mon, 18 May 2015 05:02:40 +0000</pubDate>
		<dc:creator><![CDATA[惜分飞]]></dc:creator>
				<category><![CDATA[ORACLE 12C]]></category>
		<category><![CDATA[Oracle性能优化]]></category>
		<category><![CDATA[TABLE ACCESS BY INDEX ROWID BATCHED]]></category>
		<category><![CDATA[_optimizer_batch_table_access_by_rowid]]></category>

		<guid isPermaLink="false">https://www.xifenfei.com/?p=5894</guid>
		<description><![CDATA[联系：手机/微信(+86 17813235971) QQ(107644445)  &#8230; <a href="https://www.xifenfei.com/2015/05/oracle-12c-table-access-by-index-rowid-batched.html">继续阅读 <span class="meta-nav">&#8594;</span></a>]]></description>
				<content:encoded><![CDATA[<div id="xifenfeicopyright">
<p>联系：<a href="https://www.xifenfei.com/about_xifenfei" target="_blank">手机/微信(+86 17813235971)   QQ(107644445)</a><a target="_blank" href="http://wpa.qq.com/msgrd?v=3&#038;uin=107644445&#038;site=qq&#038;menu=yes"><img src="https://www.xifenfei.com/wp-content/themes/img/site_qq.jpg" alt="QQ咨询惜分飞" title="QQ咨询惜分飞"/></a></p>
<p>标题：<a href="https://www.xifenfei.com/2015/05/oracle-12c-table-access-by-index-rowid-batched.html" target="_blank">Oracle 12C TABLE ACCESS BY INDEX ROWID BATCHED</a></p>
<p>作者：<a href="https://www.xifenfei.com" target="_blank">惜分飞</a>©版权所有[未经本人同意,不得以任何形式转载,否则有进一步追究法律责任的权利.]</p>
</div>
<p>从Oracle 12C开始执行计划中可能会出现TABLE ACCESS BY INDEX ROWID BATCHED,官方的解释：TABLE ACCESS BY INDEX ROWID BATCHED：means that the database retrieves a few rowids from the index, and then attempts to access rows in block order to improve the clustering and reduce the number of times that the database must access a block.主要意思:对于一个块中多个rowid,通过批量减少访问快的次数.而作为12.1的新特性,数据库是通过_optimizer_batch_table_access_by_rowid来控制的<br />
<br />
<strong>数据库版本12.1</strong></p>
<pre class="brush: sql; title: ; notranslate">
SQL&gt; select * from v$version;

BANNER                                                                               CON_ID
-------------------------------------------------------------------------------- ----------
Oracle Database 12c Enterprise Edition Release 12.1.0.2.0 - 64bit Production              0
PL/SQL Release 12.1.0.2.0 - Production                                                    0
CORE    12.1.0.2.0      Production                                                        0
TNS for IBM/AIX RISC System/6000: Version 12.1.0.2.0 - Production                         0
NLSRTL Version 12.1.0.2.0 - Production                                                    0
</pre>
<p>TABLE ACCESS BY INDEX ROWID BATCHED执行计划</p>
<pre class="brush: sql; title: ; notranslate">
SQL&gt; set autot traceonly exp stat;
SQL&gt; var  b1 number;
SQL&gt; set lines 150
SQL&gt; set pages 10000
SQL&gt; exec :b1:=18868701138;

PL/SQL procedure successfully completed.

SQL&gt; SELECT BRAND_ID FROM T_USERTYPE_FULLNO WHERE BILL_ID= LTRIM(:B1 ,'0') AND ROWNUM &lt; 2;


Execution Plan
----------------------------------------------------------
Plan hash value: 942613467

-----------------------------------------------------------------------------------------------------------
| Id  | Operation                            | Name               | Rows  | Bytes | Cost (%CPU)| Time     |
-----------------------------------------------------------------------------------------------------------
|   0 | SELECT STATEMENT                     |                    |     1 |    15 |     2   (0)| 00:00:01 |
|*  1 |  COUNT STOPKEY                       |                    |       |       |            |          |
|   2 |   TABLE ACCESS BY INDEX ROWID BATCHED| XIFENFEI           |     1 |    15 |     2   (0)| 00:00:01 |
|*  3 |    INDEX RANGE SCAN                  | IND_XIFENFEI       |     1 |       |     2   (0)| 00:00:01 |
-----------------------------------------------------------------------------------------------------------

Predicate Information (identified by operation id):
---------------------------------------------------

   1 - filter(ROWNUM&lt;2)
   3 - access(&quot;BILL_ID&quot;=LTRIM(:B1,'0'))


Statistics
----------------------------------------------------------
          0  recursive calls
          0  db block gets
          5  consistent gets
          0  physical reads
          0  redo size
        559  bytes sent via SQL*Net to client
        552  bytes received via SQL*Net from client
          2  SQL*Net roundtrips to/from client
          0  sorts (memory)
          0  sorts (disk)
          1  rows processed
</pre>
<p><strong>_optimizer_batch_table_access_by_rowid参数为true</strong></p>
<pre class="brush: sql; title: ; notranslate">
SQL&gt; col name for a32
SQL&gt; col value for a24
col description for a70
set linesize 150
select a.ksppinm name,b.ksppstvl value,a.ksppdesc description
SQL&gt; SQL&gt; SQL&gt;   2    from x$ksppi a,x$ksppcv b
  3   where a.inst_id = USERENV ('Instance')
  4     and b.inst_id = USERENV ('Instance')
  5     and a.indx = b.indx
  6     and upper(a.ksppinm) LIKE upper('%&amp;param%')
  7  order by name
  8  /
Enter value for param: _optimizer_batch_table_access_by_rowid
old   6:    and upper(a.ksppinm) LIKE upper('%&amp;param%')
new   6:    and upper(a.ksppinm) LIKE upper('%_optimizer_batch_table_access_by_rowid%')

NAME                                 VALUE                    DESCRIPTION
------------------------------------- ------------------------ ----------------------------------------------
_optimizer_batch_table_access_by_rowid TRUE                     enable table access by ROWID IO batching
</pre>
<p><strong>设置_optimizer_batch_table_access_by_rowid为false,执行计划由TABLE ACCESS BY INDEX ROWID BATCHED变为TABLE ACCESS BY INDEX ROWID</strong></p>
<pre class="brush: sql; title: ; notranslate">
SQL&gt; set autot traceonly exp stat;
SQL&gt; var  b1 number;
SQL&gt; set lines 150
SQL&gt; set pages 10000
SQL&gt; exec :b1:=18868701138;

PL/SQL procedure successfully completed.

SQL&gt; alter session set &quot;_optimizer_batch_table_access_by_rowid&quot;=false;

Session altered.

SQL&gt; SELECT BRAND_ID FROM XIFENFEI WHERE BILL_ID= LTRIM(:B1 ,'0') AND ROWNUM &lt; 2;


Execution Plan
----------------------------------------------------------
Plan hash value: 2797551150

---------------------------------------------------------------------------------------------------
| Id  | Operation                    | Name               | Rows  | Bytes | Cost (%CPU)| Time     |
---------------------------------------------------------------------------------------------------
|   0 | SELECT STATEMENT             |                    |     1 |    15 |     2   (0)| 00:00:01 |
|*  1 |  COUNT STOPKEY               |                    |       |       |            |          |
|   2 |   TABLE ACCESS BY INDEX ROWID| XIFENFEI           |     1 |    15 |     2   (0)| 00:00:01 |
|*  3 |    INDEX RANGE SCAN          | IND_XIFENFEI       |     1 |       |     2   (0)| 00:00:01 |
---------------------------------------------------------------------------------------------------

Predicate Information (identified by operation id):
---------------------------------------------------

   1 - filter(ROWNUM&lt;2)
   3 - access(&quot;BILL_ID&quot;=LTRIM(:B1,'0'))


Statistics
----------------------------------------------------------
          1  recursive calls
          0  db block gets
          5  consistent gets
          0  physical reads
          0  redo size
        559  bytes sent via SQL*Net to client
        552  bytes received via SQL*Net from client
          2  SQL*Net roundtrips to/from client
          0  sorts (memory)
          0  sorts (disk)
          1  rows processed
</pre>
<p><strong>optimizer_features_enable修改为11.2之后,_optimizer_batch_table_access_by_rowid会联锁变为fasle</strong></p>
<pre class="brush: sql; title: ; notranslate">
SQL&gt; alter session set optimizer_features_enable = '11.2.0.3';

Session altered.

SQL&gt; col name for a52
col value for a24
col description for a50
set linesize 150
select a.ksppinm name,b.ksppstvl value,a.ksppdesc description
  from x$ksppi a,x$ksppcv b
 where a.inst_idSQL&gt; SQL&gt; SQL&gt; SQL&gt;   2    3   = USERENV ('Instance')
   and b.inst_id = USERENV ('Instance')
   and a.indx = b.indx
   and upper(a.ksppinm) LIKE upper('%&amp;param%')
order by name
  4    5    6    7    8  /
Enter value for param: _optimizer_batch_table_access_by
old   6:    and upper(a.ksppinm) LIKE upper('%&amp;param%')
new   6:    and upper(a.ksppinm) LIKE upper('%_optimizer_batch_table_access_by%')

NAME                                       VALUE          DESCRIPTION
------------------------------------------ -------------- -----------------------------------------
_optimizer_batch_table_access_by_rowid     FALSE          enable table access by ROWID IO batching
</pre>
<p>这里可以看出来,在调整optimizer_features_enable参数后,会直接影响某些数据库相关的优化器参数,例如:_optimizer_batch_table_access_by_rowid</p>
<div id="crp_related"><ul><li style="list-style-type:decimal;font-size:11px;" ><a href="https://www.xifenfei.com/2017/06/_optimizer_null_aware_antijoin-not-in.html" rel="bookmark" class="crp_title">_optimizer_null_aware_antijoin和not in效率</a></li><li style="list-style-type:decimal;font-size:11px;" ><a href="https://www.xifenfei.com/2012/05/bind-variable-peeking-%e6%b5%8b%e8%af%95.html" rel="bookmark" class="crp_title">Bind Variable Peeking 测试</a></li><li style="list-style-type:decimal;font-size:11px;" ><a href="https://www.xifenfei.com/2012/12/%e5%88%9b%e5%bb%ba%e6%94%af%e6%8c%81null-index.html" rel="bookmark" class="crp_title">创建包含null值index</a></li><li style="list-style-type:decimal;font-size:11px;" ><a href="https://www.xifenfei.com/2013/01/%e8%ae%be%e7%bd%ae_smu_debug_mode%e5%ae%9e%e7%8e%b0%e6%8c%87%e5%ae%9asession%e7%ba%a7%e5%88%ab%e4%bd%bf%e7%94%a8%e7%89%b9%e5%ae%9a%e5%9b%9e%e6%bb%9a%e6%ae%b5.html" rel="bookmark" class="crp_title">设置_smu_debug_mode实现指定session级别使用特定回滚段</a></li><li style="list-style-type:decimal;font-size:11px;" ><a href="https://www.xifenfei.com/2012/04/%e6%89%a7%e8%a1%8c%e8%ae%a1%e5%88%92%e4%b8%ad%e5%b8%b8%e8%a7%81index%e8%ae%bf%e9%97%ae%e6%96%b9%e5%bc%8f.html" rel="bookmark" class="crp_title">执行计划中常见index访问方式</a></li><li style="list-style-type:decimal;font-size:11px;" ><a href="https://www.xifenfei.com/2020/01/heatmap-segment-size-is-large.html" rel="bookmark" class="crp_title">sysaux中HEATMAP 对象较大</a></li><li style="list-style-type:decimal;font-size:11px;" ><a href="https://www.xifenfei.com/2014/03/%e5%90%abis-null-sql%e8%af%ad%e5%8f%a5%e4%bc%98%e5%8c%96.html" rel="bookmark" class="crp_title">含is null sql语句优化</a></li><li style="list-style-type:decimal;font-size:11px;" ><a href="https://www.xifenfei.com/2011/09/10g%e6%96%b0%e5%a2%9e%e5%88%97%e6%96%b9%e5%bc%8f%e6%8c%87%e5%ae%9ahint.html" rel="bookmark" class="crp_title">10g新增列方式指定HINT</a></li><li style="list-style-type:decimal;font-size:11px;" ><a href="https://www.xifenfei.com/2014/10/11g%e4%b8%ad-connect-by-%e8%af%ad%e5%8f%a5%e6%89%a7%e8%a1%8c%e8%ae%a1%e5%88%92%e6%94%b9%e5%8f%98.html" rel="bookmark" class="crp_title">11g中 connect by 语句执行计划改变</a></li><li style="list-style-type:decimal;font-size:11px;" ><a href="https://www.xifenfei.com/2012/04/hint%e6%8c%87%e5%ae%9aindex%e7%9a%84%e6%b7%b1%e5%85%a5%e7%90%86%e8%a7%a3.html" rel="bookmark" class="crp_title">hint指定index的深入理解</a></li><li style="list-style-type:decimal;font-size:11px;" ><a href="https://www.xifenfei.com/2011/07/select-maxamina-from-table%e4%bc%98%e5%8c%96.html" rel="bookmark" class="crp_title">select max(id),min(id) from table优化</a></li><li style="list-style-type:decimal;font-size:11px;" ><a href="https://www.xifenfei.com/2013/08/oracle-12c-partial-globallocal-indexes-for-partitioned-tables.html" rel="bookmark" class="crp_title">ORACLE 12C Partial Global/Local Indexes for Partitioned Tables</a></li></ul></div>]]></content:encoded>
			<wfw:commentRss>https://www.xifenfei.com/2015/05/oracle-12c-table-access-by-index-rowid-batched.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>11g中 connect by 语句执行计划改变</title>
		<link>https://www.xifenfei.com/2014/10/11g%e4%b8%ad-connect-by-%e8%af%ad%e5%8f%a5%e6%89%a7%e8%a1%8c%e8%ae%a1%e5%88%92%e6%94%b9%e5%8f%98.html</link>
		<comments>https://www.xifenfei.com/2014/10/11g%e4%b8%ad-connect-by-%e8%af%ad%e5%8f%a5%e6%89%a7%e8%a1%8c%e8%ae%a1%e5%88%92%e6%94%b9%e5%8f%98.html#comments</comments>
		<pubDate>Mon, 27 Oct 2014 14:34:11 +0000</pubDate>
		<dc:creator><![CDATA[惜分飞]]></dc:creator>
				<category><![CDATA[Oracle性能优化]]></category>
		<category><![CDATA[connect_by_filtering]]></category>

		<guid isPermaLink="false">https://www.xifenfei.com/?p=5585</guid>
		<description><![CDATA[联系：手机/微信(+86 17813235971) QQ(107644445)  &#8230; <a href="https://www.xifenfei.com/2014/10/11g%e4%b8%ad-connect-by-%e8%af%ad%e5%8f%a5%e6%89%a7%e8%a1%8c%e8%ae%a1%e5%88%92%e6%94%b9%e5%8f%98.html">继续阅读 <span class="meta-nav">&#8594;</span></a>]]></description>
				<content:encoded><![CDATA[<div id="xifenfeicopyright">
<p>联系：<a href="https://www.xifenfei.com/about_xifenfei" target="_blank">手机/微信(+86 17813235971)   QQ(107644445)</a><a target="_blank" href="http://wpa.qq.com/msgrd?v=3&#038;uin=107644445&#038;site=qq&#038;menu=yes"><img src="https://www.xifenfei.com/wp-content/themes/img/site_qq.jpg" alt="QQ咨询惜分飞" title="QQ咨询惜分飞"/></a></p>
<p>标题：<a href="https://www.xifenfei.com/2014/10/11g%e4%b8%ad-connect-by-%e8%af%ad%e5%8f%a5%e6%89%a7%e8%a1%8c%e8%ae%a1%e5%88%92%e6%94%b9%e5%8f%98.html" target="_blank">11g中 connect by 语句执行计划改变</a></p>
<p>作者：<a href="https://www.xifenfei.com" target="_blank">惜分飞</a>©版权所有[未经本人同意,不得以任何形式转载,否则有进一步追究法律责任的权利.]</p>
</div>
<p>从10.2.0.3升级到11.2.0.4的朋友，如果细心会发现，以下sql在11.2.0.4中执行效率变低(该sql主要是获取连接用户获取权限信息)<br />
select privilege#,level from sysauth$ connect by grantee#=prior privilege# and privilege#>0 start with grantee#=:1 and privilege#>0<br />
如果你接触是Oracle版本比较多,而且还比较细心,你可能会进一步发现在11.2.0.2中该条sql是:select /*+ connect_by_filtering */ privilege#, level from sysauth$ connect by grantee#=prior privilege# and privilege#>0 start with grantee#=:1 and privilege#>0 也就是说使用了/*+ connect_by_filtering */提示.我这里通过简单测试说明问题.<br />
<br />
<strong>在11.2.0.4环境中</strong></p>
<pre class="brush: bash; title: ; notranslate">
14:16:19 SQL&gt; set autot trace exp stat
14:16:20 SQL&gt; set time on
14:16:20 SQL&gt; set timing on
14:16:20 SQL&gt; var a1 number;
14:16:20 SQL&gt; exec :a1:=6;

PL/SQL 过程已成功完成。

已用时间:  00: 00: 00.00
14:16:20 SQL&gt; select privilege#,level from sysauth$ connect by grantee#=prior 
14:16:20 SQL&gt; privilege# and privilege#&gt;0 start with grantee#=:a1  and privilege#&gt;0
14:16:22 SQL&gt; /

已用时间:  00: 00: 00.01

执行计划
----------------------------------------------------------
Plan hash value: 2624122540

------------------------------------------------------------------------------------------------------
| Id  | Operation                               | Name       | Rows  | Bytes | Cost (%CPU)| Time     |
------------------------------------------------------------------------------------------------------
|   0 | SELECT STATEMENT                        |            |     7 |   182 |     3  (34)| 00:00:01 |
|*  1 |  CONNECT BY NO FILTERING WITH START-WITH|            |       |       |            |          |
|   2 |   INDEX FAST FULL SCAN                  | I_SYSAUTH1 |   618 |  4944 |     2   (0)| 00:00:01 |
------------------------------------------------------------------------------------------------------

Predicate Information (identified by operation id):
---------------------------------------------------

   1 - access(&quot;GRANTEE#&quot;=PRIOR &quot;PRIVILEGE#&quot;)
       filter(&quot;PRIVILEGE#&quot;&gt;0 AND &quot;GRANTEE#&quot;=TO_NUMBER(:A1) AND &quot;PRIVILEGE#&quot;&gt;0)


统计信息
----------------------------------------------------------
          1  recursive calls
          0  db block gets
          7  consistent gets
          0  physical reads
          0  redo size
        599  bytes sent via SQL*Net to client
        520  bytes received via SQL*Net from client
          2  SQL*Net roundtrips to/from client
          2  sorts (memory)
          0  sorts (disk)
          1  rows processed
</pre>
<p>这里可以看出来这里使用的执行计划使用了CONNECT BY NO FILTERING WITH START-WITH,逻辑读为7.<br />
<br />
<strong>10.2.0.3环境中</strong></p>
<pre class="brush: sql; title: ; notranslate">
14:32:57 SQL&gt; set lines 150
14:33:00 SQL&gt; set autot trace exp stat
14:33:01 SQL&gt; set time on
14:33:01 SQL&gt; set timing on
14:33:01 SQL&gt; var a1 number;
14:33:01 SQL&gt; exec :a1:=6;

PL/SQL procedure successfully completed.

Elapsed: 00:00:00.00
14:33:01 SQL&gt; select privilege#,level from sysauth$ connect by grantee#=prior 
14:33:01 SQL&gt; privilege# and privilege#&gt;0 start with grantee#=:a1  and privilege#&gt;0  ;

Elapsed: 00:00:00.00

Execution Plan
----------------------------------------------------------
Plan hash value: 2620769641

----------------------------------------------------------------------------------------
| Id  | Operation                 | Name       | Rows  | Bytes | Cost (%CPU)| Time     |
----------------------------------------------------------------------------------------
|   0 | SELECT STATEMENT          |            |     3 |    24 |     2   (0)| 00:00:01 |
|*  1 |  CONNECT BY WITH FILTERING|            |       |       |            |          |
|*  2 |   INDEX RANGE SCAN        | I_SYSAUTH1 |     3 |    24 |     2   (0)| 00:00:01 |
|   3 |   NESTED LOOPS            |            |       |       |            |          |
|   4 |    CONNECT BY PUMP        |            |       |       |            |          |
|*  5 |    INDEX RANGE SCAN       | I_SYSAUTH1 |     3 |    24 |     2   (0)| 00:00:01 |
----------------------------------------------------------------------------------------

Predicate Information (identified by operation id):
---------------------------------------------------

   1 - access(&quot;GRANTEE#&quot;=PRIOR &quot;PRIVILEGE#&quot;)
       filter(&quot;PRIVILEGE#&quot;&gt;0)
   2 - access(&quot;GRANTEE#&quot;=TO_NUMBER(:A1) AND &quot;PRIVILEGE#&quot;&gt;0)
   5 - access(&quot;GRANTEE#&quot;=PRIOR &quot;PRIVILEGE#&quot; AND &quot;PRIVILEGE#&quot;&gt;0)


Statistics
----------------------------------------------------------
          0  recursive calls
          0  db block gets
          4  consistent gets
          0  physical reads
          0  redo size
        583  bytes sent via SQL*Net to client
        492  bytes received via SQL*Net from client
          2  SQL*Net roundtrips to/from client
          3  sorts (memory)
          0  sorts (disk)
          1  rows processed
</pre>
<p>这里执行计划使用的为CONNECT BY WITH FILTERING,而且逻辑读为4,对于这个sql来说,使用CONNECT BY WITH FILTERING执行效率更高.<br />
<br />
这里可以很明显的看到:connect by查询的执行计划从10g的CONNECT BY WITH FILTERING变为了11g中的CONNECT BY NO FILTERING WITH SW (UNIQUE)，从而使得执行计划发生改变。但是Oracle一般有个特性,就是当引入新特性之时,一般都会伴随隐含参数或者event来屏蔽新特性.这里也例外,我们可以通过&#8221;_optimizer_connect_by_elim_dups&#8221; = false和&#8221;_connect_by_use_union_all&#8221; = &#8220;old_plan_mode&#8221;来屏蔽11g中关于connect by执行计划的改变,使得执行计划恢复到10G的CONNECT BY WITH FILTERING方式</p>
<pre class="brush: sql; title: ; notranslate">
14:30:45 SQL&gt; alter session set &quot;_optimizer_connect_by_elim_dups&quot; = false;

会话已更改。

已用时间:  00: 00: 00.00
14:30:46 SQL&gt; alter session set &quot;_connect_by_use_union_all&quot; = &quot;old_plan_mode&quot;;

会话已更改。

已用时间:  00: 00: 00.00
14:30:46 SQL&gt; set autot trace exp stat
14:30:46 SQL&gt; set time on
14:30:46 SQL&gt; set timing on
14:30:46 SQL&gt; var a1 number;
14:30:46 SQL&gt; exec :a1:=6;

PL/SQL 过程已成功完成。

已用时间:  00: 00: 00.00
14:30:46 SQL&gt; select privilege#,level from sysauth$ connect by grantee#=prior 
14:30:46 SQL&gt; privilege# and privilege#&gt;0 start with grantee#=:a1  and privilege#&gt;0 ;

已用时间:  00: 00: 00.01

执行计划
----------------------------------------------------------
Plan hash value: 2620769641

----------------------------------------------------------------------------------------
| Id  | Operation                 | Name       | Rows  | Bytes | Cost (%CPU)| Time     |
----------------------------------------------------------------------------------------
|   0 | SELECT STATEMENT          |            |     2 |    16 |     2   (0)| 00:00:01 |
|*  1 |  CONNECT BY WITH FILTERING|            |       |       |            |          |
|*  2 |   INDEX RANGE SCAN        | I_SYSAUTH1 |     2 |    16 |     2   (0)| 00:00:01 |
|   3 |   NESTED LOOPS            |            |       |       |            |          |
|   4 |    CONNECT BY PUMP        |            |       |       |            |          |
|*  5 |    INDEX RANGE SCAN       | I_SYSAUTH1 |     2 |    16 |     2   (0)| 00:00:01 |
----------------------------------------------------------------------------------------

Predicate Information (identified by operation id):
---------------------------------------------------

   1 - access(&quot;GRANTEE#&quot;=PRIOR &quot;PRIVILEGE#&quot;)
       filter(&quot;PRIVILEGE#&quot;&gt;0)
   2 - access(&quot;GRANTEE#&quot;=TO_NUMBER(:A1) AND &quot;PRIVILEGE#&quot;&gt;0)
   5 - access(&quot;GRANTEE#&quot;=PRIOR &quot;PRIVILEGE#&quot; AND &quot;PRIVILEGE#&quot;&gt;0)


统计信息
----------------------------------------------------------
          1  recursive calls
          0  db block gets
          4  consistent gets
          0  physical reads
          0  redo size
        599  bytes sent via SQL*Net to client
        520  bytes received via SQL*Net from client
          2  SQL*Net roundtrips to/from client
          3  sorts (memory)
          0  sorts (disk)
          1  rows processed
</pre>
<p>11.2.0.2中也许是考虑到connect by 不够成熟,因此使用了hint /*+ connect_by_filtering */ 来固定执行计划</p>
<pre class="brush: sql; title: ; notranslate">
14:22:09 SQL&gt; select /*+ connect_by_filtering */ privilege#,level from sysauth$ connect by grantee#=prior
14:22:09 SQL&gt;  privilege# and privilege#&gt;0 start with grantee#=:a1  and privilege#&gt;0 
14:22:10 SQL&gt; /

已用时间:  00: 00: 00.00

执行计划
----------------------------------------------------------
Plan hash value: 2620769641

----------------------------------------------------------------------------------------
| Id  | Operation                 | Name       | Rows  | Bytes | Cost (%CPU)| Time     |
----------------------------------------------------------------------------------------
|   0 | SELECT STATEMENT          |            |     7 |   182 |     8  (25)| 00:00:01 |
|*  1 |  CONNECT BY WITH FILTERING|            |       |       |            |          |
|*  2 |   INDEX RANGE SCAN        | I_SYSAUTH1 |     2 |    16 |     2   (0)| 00:00:01 |
|   3 |   NESTED LOOPS            |            |     5 |   105 |     4   (0)| 00:00:01 |
|   4 |    CONNECT BY PUMP        |            |       |       |            |          |
|*  5 |    INDEX RANGE SCAN       | I_SYSAUTH1 |     2 |    16 |     1   (0)| 00:00:01 |
----------------------------------------------------------------------------------------

Predicate Information (identified by operation id):
---------------------------------------------------

   1 - access(&quot;GRANTEE#&quot;=PRIOR &quot;PRIVILEGE#&quot;)
       filter(&quot;PRIVILEGE#&quot;&gt;0)
   2 - access(&quot;GRANTEE#&quot;=TO_NUMBER(:A1) AND &quot;PRIVILEGE#&quot;&gt;0)
   5 - access(&quot;GRANTEE#&quot;=&quot;connect$_by$_pump$_002&quot;.&quot;prior privilege# &quot; AND
              &quot;PRIVILEGE#&quot;&gt;0)


统计信息
----------------------------------------------------------
          1  recursive calls
          0  db block gets
          4  consistent gets
          0  physical reads
          0  redo size
        599  bytes sent via SQL*Net to client
        520  bytes received via SQL*Net from client
          2  SQL*Net roundtrips to/from client
          3  sorts (memory)
          0  sorts (disk)
          1  rows processed
</pre>
<p>CONNECT BY NO FILTERING WITH SW (UNIQUE)和CONNECT BY WITH FILTERING,没有明显的优劣之分,只有在特定的情况下,进行了实际的测试,选择合适自己的sql的执行计划</p>
<div id="crp_related"><ul><li style="list-style-type:decimal;font-size:11px;" ><a href="https://www.xifenfei.com/2025/01/grant-public-sql.html" rel="bookmark" class="crp_title">public授权语句</a></li><li style="list-style-type:decimal;font-size:11px;" ><a href="https://www.xifenfei.com/2011/11/oracle%e5%b8%b8%e7%94%a8%e7%94%a8%e6%88%b7%e6%9d%83%e9%99%90%e8%a7%86%e5%9b%be.html" rel="bookmark" class="crp_title">Oracle常用用户权限视图</a></li><li style="list-style-type:decimal;font-size:11px;" ><a href="https://www.xifenfei.com/2025/03/grant-dml-to-public-authorization-expires.html" rel="bookmark" class="crp_title">表dml操作权限授权给public,导致只读用户失效</a></li><li style="list-style-type:decimal;font-size:11px;" ><a href="https://www.xifenfei.com/2014/03/%e5%90%abis-null-sql%e8%af%ad%e5%8f%a5%e4%bc%98%e5%8c%96.html" rel="bookmark" class="crp_title">含is null sql语句优化</a></li><li style="list-style-type:decimal;font-size:11px;" ><a href="https://www.xifenfei.com/2013/04/12c-top-n-sql%e5%ae%9e%e7%8e%b0%e5%88%86%e9%a1%b5%e5%8a%9f%e8%83%bd.html" rel="bookmark" class="crp_title">ORACLE 12C TOP N SQL实现分页功能</a></li><li style="list-style-type:decimal;font-size:11px;" ><a href="https://www.xifenfei.com/2012/04/%e6%89%a7%e8%a1%8c%e8%ae%a1%e5%88%92%e4%b8%ad%e5%b8%b8%e8%a7%81index%e8%ae%bf%e9%97%ae%e6%96%b9%e5%bc%8f.html" rel="bookmark" class="crp_title">执行计划中常见index访问方式</a></li><li style="list-style-type:decimal;font-size:11px;" ><a href="https://www.xifenfei.com/2013/08/oracle-12c-partial-globallocal-indexes-for-partitioned-tables.html" rel="bookmark" class="crp_title">ORACLE 12C Partial Global/Local Indexes for Partitioned Tables</a></li><li style="list-style-type:decimal;font-size:11px;" ><a href="https://www.xifenfei.com/2011/07/select-maxamina-from-table%e4%bc%98%e5%8c%96.html" rel="bookmark" class="crp_title">select max(id),min(id) from table优化</a></li><li style="list-style-type:decimal;font-size:11px;" ><a href="https://www.xifenfei.com/2012/12/%e5%88%9b%e5%bb%ba%e6%94%af%e6%8c%81null-index.html" rel="bookmark" class="crp_title">创建包含null值index</a></li><li style="list-style-type:decimal;font-size:11px;" ><a href="https://www.xifenfei.com/2017/06/_optimizer_null_aware_antijoin-not-in.html" rel="bookmark" class="crp_title">_optimizer_null_aware_antijoin和not in效率</a></li><li style="list-style-type:decimal;font-size:11px;" ><a href="https://www.xifenfei.com/2011/09/oracle%e7%9b%b4%e6%96%b9%e5%9b%be%e7%90%86%e8%a7%a3%e4%b8%8e%e5%ae%9e%e9%aa%8c.html" rel="bookmark" class="crp_title">Oracle直方图理解与实验</a></li><li style="list-style-type:decimal;font-size:11px;" ><a href="https://www.xifenfei.com/2011/09/10g%e6%96%b0%e5%a2%9e%e5%88%97%e6%96%b9%e5%bc%8f%e6%8c%87%e5%ae%9ahint.html" rel="bookmark" class="crp_title">10g新增列方式指定HINT</a></li></ul></div>]]></content:encoded>
			<wfw:commentRss>https://www.xifenfei.com/2014/10/11g%e4%b8%ad-connect-by-%e8%af%ad%e5%8f%a5%e6%89%a7%e8%a1%8c%e8%ae%a1%e5%88%92%e6%94%b9%e5%8f%98.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>执行计划改变导致数据库负载过高</title>
		<link>https://www.xifenfei.com/2014/05/%e6%89%a7%e8%a1%8c%e8%ae%a1%e5%88%92%e6%94%b9%e5%8f%98%e5%af%bc%e8%87%b4%e6%95%b0%e6%8d%ae%e5%ba%93%e8%b4%9f%e8%bd%bd%e8%bf%87%e9%ab%98.html</link>
		<comments>https://www.xifenfei.com/2014/05/%e6%89%a7%e8%a1%8c%e8%ae%a1%e5%88%92%e6%94%b9%e5%8f%98%e5%af%bc%e8%87%b4%e6%95%b0%e6%8d%ae%e5%ba%93%e8%b4%9f%e8%bd%bd%e8%bf%87%e9%ab%98.html#comments</comments>
		<pubDate>Tue, 13 May 2014 03:19:21 +0000</pubDate>
		<dc:creator><![CDATA[惜分飞]]></dc:creator>
				<category><![CDATA[Oracle性能优化]]></category>
		<category><![CDATA[sql profile]]></category>
		<category><![CDATA[数据库性能优化]]></category>

		<guid isPermaLink="false">https://www.xifenfei.com/?p=5309</guid>
		<description><![CDATA[联系：手机/微信(+86 17813235971) QQ(107644445)  &#8230; <a href="https://www.xifenfei.com/2014/05/%e6%89%a7%e8%a1%8c%e8%ae%a1%e5%88%92%e6%94%b9%e5%8f%98%e5%af%bc%e8%87%b4%e6%95%b0%e6%8d%ae%e5%ba%93%e8%b4%9f%e8%bd%bd%e8%bf%87%e9%ab%98.html">继续阅读 <span class="meta-nav">&#8594;</span></a>]]></description>
				<content:encoded><![CDATA[<div id="xifenfeicopyright">
<p>联系：<a href="https://www.xifenfei.com/about_xifenfei" target="_blank">手机/微信(+86 17813235971)   QQ(107644445)</a><a target="_blank" href="http://wpa.qq.com/msgrd?v=3&#038;uin=107644445&#038;site=qq&#038;menu=yes"><img src="https://www.xifenfei.com/wp-content/themes/img/site_qq.jpg" alt="QQ咨询惜分飞" title="QQ咨询惜分飞"/></a></p>
<p>标题：<a href="https://www.xifenfei.com/2014/05/%e6%89%a7%e8%a1%8c%e8%ae%a1%e5%88%92%e6%94%b9%e5%8f%98%e5%af%bc%e8%87%b4%e6%95%b0%e6%8d%ae%e5%ba%93%e8%b4%9f%e8%bd%bd%e8%bf%87%e9%ab%98.html" target="_blank">执行计划改变导致数据库负载过高</a></p>
<p>作者：<a href="https://www.xifenfei.com" target="_blank">惜分飞</a>©版权所有[未经本人同意,不得以任何形式转载,否则有进一步追究法律责任的权利.]</p>
</div>
<p>核心生产库突然负载飙升,我的压力来了,通过分析是一条sql的执行计划改变引起该故障,最终通过sql profile固定执行计划解决该问题<br />
<strong>数据库主机负载</strong><br />
这里明显表现系统load 偏高，而且还在上升中；top的进程中，占用cpu都计划100%</p>
<pre class="brush: bash; title: ; notranslate">
top - 16:25:39 up 123 days,  1:42,  4 users,  load average: 46.19, 45.08, 43.93
Tasks: 1469 total,  28 running, 1439 sleeping,   0 stopped,   2 zombie
Cpu(s): 45.9%us,  1.1%sy,  0.0%ni, 47.1%id,  5.2%wa,  0.1%hi,  0.6%si,  0.0%st
Mem:  264253752k total, 262605260k used,  1648492k free,   413408k buffers
Swap: 33554424k total,   458684k used, 33095740k free, 67110504k cached

  PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND                    
 2622 oracle    18   0  150g  34m  28m R 100.0  0.0  11:58.21 oracleq9db1 (LOCAL=NO)    
15881 oracle    21   0  150g  35m  28m R 100.0  0.0  72:14.20 oracleq9db1 (LOCAL=NO)    
17214 oracle    19   0  150g  38m  32m R 100.0  0.0  20:47.44 oracleq9db1 (LOCAL=NO)    
17705 oracle    21   0  150g  34m  28m R 100.0  0.0  27:33.00 oracleq9db1 (LOCAL=NO)    
 6110 oracle    19   0  150g  34m  28m R 99.8  0.0  12:33.34 oracleq9db1 (LOCAL=NO)     
 6876 oracle    19   0  150g  34m  27m R 99.5  0.0  12:43.90 oracleq9db1 (LOCAL=NO)     
17205 oracle    23   0  150g  34m  27m R 99.5  0.0  21:37.18 oracleq9db1 (LOCAL=NO)     
24629 oracle    20   0  150g  35m  29m R 99.5  0.0  28:10.62 oracleq9db1 (LOCAL=NO)     
26959 oracle    19   0  150g  34m  27m R 99.5  0.0  47:17.87 oracleq9db1 (LOCAL=NO)     
 7655 oracle    18   0  150g  30m  25m R 98.5  0.0   2:28.45 oracleq9db1 (LOCAL=NO)     
16377 oracle    18   0  150g  34m  28m R 98.5  0.0  36:07.11 oracleq9db1 (LOCAL=NO)     
24637 oracle    18   0  150g  37m  30m R 98.2  0.0  26:39.15 oracleq9db1 (LOCAL=NO)     
 6106 oracle    21   0  150g  40m  33m R 97.2  0.0  11:37.75 oracleq9db1 (LOCAL=NO)     
28785 oracle    18   0  150g  34m  28m R 96.9  0.0  24:03.29 oracleq9db1 (LOCAL=NO)     
24278 oracle    17   0  150g  31m  26m S 96.5  0.0   3:15.51 oracleq9db1 (LOCAL=NO)     
24283 oracle    17   0  150g  33m  28m S 96.5  0.0   6:25.26 oracleq9db1 (LOCAL=NO)     
 7098 oracle    18   0  150g  32m  27m R 94.6  0.0   2:20.22 oracleq9db1 (LOCAL=NO)     
 6874 oracle    17   0  150g  34m  28m R 87.0  0.0  12:02.92 oracleq9db1 (LOCAL=NO)     
18206 oracle    16   0  150g  34m  27m R 86.1  0.0  16:11.28 oracleq9db1 (LOCAL=NO)     
 7096 oracle    17   0  150g  29m  24m R 85.4  0.0   3:01.72 oracleq9db1 (LOCAL=NO)     
</pre>
<p><strong>数据库等待事件</strong></p>
<pre class="brush: sql; title: ; notranslate">
       SID EVENT
---------- ----------------------------------------------------------------
       183 gc cr request
       185 latch: cache buffers chains
       239 db file sequential read
       292 gc cr request
       406 gc cr request
       410 db file sequential read
       463 gc current request
       572 gc buffer busy acquire
       575 gc buffer busy acquire
       577 latch: cache buffers chains
       629 db file sequential read
       747 gc cr request
       919 latch: cache buffers chains
       974 gc cr request
      1033 log file sync
      1141 db file parallel write
      1153 gc cr request
      1199 db file sequential read
      1378 db file sequential read
      1495 gc cr request
      1540 db file parallel write
      1547 gc buffer busy acquire
      1662 gc cr request
      1715 gc buffer busy acquire
      1770 SQL*Net message to client
      1830 latch: cache buffers chains
      1884 gc cr request
      2113 db file sequential read
      2173 db file sequential read
      2229 rdbms ipc reply
      2292 db file sequential read
      2341 db file sequential read
      2348 gc cr request
      2460 gc cr request
      2632 gc cr request
      2684 gc cr request
      2687 db file sequential read
      2749 db file sequential read
      2913 gc cr request
      2967 db file sequential read
      3038 gc cr request
      3087 SQL*Net message to client
      3089 gc cr request
      3194 db file sequential read
      3195 db file sequential read
      3309 latch: cache buffers chains
      3371 gc cr request
      3485 gc cr request
      3535 gc cr request
</pre>
<p>可以这里有很多gc cr request等待和cache buffers chains等待，第一反应就是很可能系统某条sql执行计划不正确导致逻辑读剧增.<br />
<br />
<strong>分析awr报告</strong><br />
故障时候的逻辑读 top sql可以看出来cdwjdd67x27mh的sql逻辑读异常大<br />
<img src="//www.xifenfei.com/wp-content/uploads/2014/05/awr1.png" alt="awr1" width="919" height="154" class="alignleft size-full wp-image-5310" /><br />
分析正常时间点awr报告中cdwjdd67x27mh逻辑读情况<br />
<img src="//www.xifenfei.com/wp-content/uploads/2014/05/awr2.png" alt="awr2" width="917" height="303" class="alignleft size-full wp-image-5311" /><br />
通过对比可以发现两个awr中，cdwjdd67x27mh 语句执行次数差不多，但是单次逻辑读从800多突变为34000多，增加了40多倍</p>
<p><strong>cdwjdd67x27mh 语句分析</strong><br />
执行计划</p>
<pre class="brush: sql; title: ; notranslate">
17:36:08 sys@Q9DB&gt;select * from table(dbms_xplan.display_awr('cdwjdd67x27mh'));

PLAN_TABLE_OUTPUT
-----------------------------------------------------------------------------------------------------------------------------------------------------------------
SQL_ID cdwjdd67x27mh
--------------------
select * from ( select          *                               from                            GE_TAOBAO_BILL           o 
                 WHERE 1=1                       and
o.CREATED_TIME &gt;= :1            and o.CREATED_TIME &lt; :2                    
                                and o.REC_SITE_ID = :3                                
             and o.STATUS_ID = :4             
             and o.SERVICE_TYPE = :5 ) where rownum
&lt;= 36000

Plan hash value: 647855111

----------------------------------------------------------------------------------------------------------------------------------
| Id  | Operation                            | Name                      | Rows  | Bytes | Cost (%CPU)| Time     | Pstart| Pstop |
----------------------------------------------------------------------------------------------------------------------------------
|   0 | SELECT STATEMENT                     |                           |       |       |     5 (100)|          |        |
|   1 |  COUNT STOPKEY                       |                           |       |       |            |          |        |
|   2 |   FILTER                             |                           |       |       |            |          |        |
|   3 |    PARTITION RANGE ITERATOR          |                           |     1 |   455 |     5   (0)| 00:00:01 |   KEY |   KEY |
|   4 |     TABLE ACCESS BY LOCAL INDEX ROWID| GE_TAOBAO_BILL            |     1 |   455 |     5   (0)| 00:00:01 |   KEY |   KEY |
|   5 |      INDEX RANGE SCAN                | IDX_TAOBAO_BILL_CR_ISDP_S |     1 |       |     4   (0)| 00:00:01 |   KEY |   KEY |
----------------------------------------------------------------------------------------------------------------------------------

SQL_ID cdwjdd67x27mh
--------------------
select * from ( select          *                               from                            GE_TAOBAO_BILL           o 
                 WHERE 1=1                       and
o.CREATED_TIME &gt;= :1            and o.CREATED_TIME &lt; :2                    
                                and o.REC_SITE_ID = :3                                
             and o.STATUS_ID = :4   
             and o.SERVICE_TYPE = :5 ) where rownum
&lt;= 36000

Plan hash value: 2979024279

---------------------------------------------------------------------------------------------------------------------------------
| Id  | Operation                            | Name                     | Rows  | Bytes | Cost (%CPU)| Time     | Pstart| Pstop |
---------------------------------------------------------------------------------------------------------------------------------
|   0 | SELECT STATEMENT                     |                          |       |       |    13 (100)|          |       ||
|   1 |  COUNT STOPKEY                       |                          |       |       |            |          |       ||
|   2 |   FILTER                             |                          |       |       |            |          |       ||
|   3 |    PARTITION RANGE ITERATOR          |                          |     1 |   455 |    13   (0)| 00:00:01 |   KEY |   KEY |
|   4 |     TABLE ACCESS BY LOCAL INDEX ROWID| GE_TAOBAO_BILL           |     1 |   455 |    13   (0)| 00:00:01 |   KEY |   KEY |
|   5 |      INDEX RANGE SCAN                | IDX_TAOBAO_BILL_CR_REC_S |     4 |       |     9   (0)| 00:00:01 |   KEY |   KEY |
---------------------------------------------------------------------------------------------------------------------------------
</pre>
<p>这里可以发现cdwjdd67x27mh在数据库中有两个执行计划<br />
<br />
通过awr数据，看执行计划的变化情况</p>
<pre class="brush: sql; title: ; notranslate">
10:50:29 sys@Q9DB&gt;select a.INSTANCE_NUMBER,a.snap_id,a.sql_id,a.plan_hash_value,b.begin_interval_time
10:50:30   2  from dba_hist_sqlstat a, dba_hist_snapshot b 
10:50:30   3  where sql_id ='cdwjdd67x27mh' 
10:50:30   4  and a.snap_id = b.snap_id 
10:50:30   5  order by instance_number,begin_interval_time  desc;

INSTANCE_NUMBER    SNAP_ID SQL_ID        PLAN_HASH_VALUE BEGIN_INTERVAL_TIME
--------------- ---------- ------------- --------------- ----------------------------------------
              1      20719 cdwjdd67x27mh      2979024279 12-MAY-14 05.00.12.753 PM
              1      20719 cdwjdd67x27mh       647855111 12-MAY-14 05.00.12.753 PM
              1      20719 cdwjdd67x27mh      2979024279 12-MAY-14 05.00.12.702 PM
              1      20719 cdwjdd67x27mh       647855111 12-MAY-14 05.00.12.702 PM
              1      20718 cdwjdd67x27mh       647855111 12-MAY-14 04.00.24.197 PM
              1      20718 cdwjdd67x27mh      2979024279 12-MAY-14 04.00.24.197 PM
              1      20718 cdwjdd67x27mh       647855111 12-MAY-14 04.00.24.172 PM
              1      20718 cdwjdd67x27mh      2979024279 12-MAY-14 04.00.24.172 PM
              1      20717 cdwjdd67x27mh       647855111 12-MAY-14 03.11.22.251 PM
              1      20717 cdwjdd67x27mh      2979024279 12-MAY-14 03.11.22.251 PM
              1      20717 cdwjdd67x27mh       647855111 12-MAY-14 03.11.22.188 PM
              1      20717 cdwjdd67x27mh      2979024279 12-MAY-14 03.11.22.188 PM
              ………………
              1      20696 cdwjdd67x27mh      2979024279 11-MAY-14 07.00.07.142 PM
              1      20696 cdwjdd67x27mh      2979024279 11-MAY-14 07.00.07.105 PM
              1      20695 cdwjdd67x27mh      2979024279 11-MAY-14 06.00.12.771 PM
              1      20695 cdwjdd67x27mh      2979024279 11-MAY-14 06.00.12.707 PM
              1      20694 cdwjdd67x27mh      2979024279 11-MAY-14 05.00.48.249 PM
              1      20694 cdwjdd67x27mh      2979024279 11-MAY-14 05.00.48.170 PM
              1      20693 cdwjdd67x27mh      2979024279 11-MAY-14 04.00.37.841 PM
              …………
              2      20719 cdwjdd67x27mh      2979024279 12-MAY-14 05.00.12.753 PM
              2      20719 cdwjdd67x27mh      2979024279 12-MAY-14 05.00.12.702 PM
              2      20718 cdwjdd67x27mh      2979024279 12-MAY-14 04.00.24.197 PM
              2      20718 cdwjdd67x27mh      2979024279 12-MAY-14 04.00.24.172 PM
              2      20717 cdwjdd67x27mh      2979024279 12-MAY-14 03.11.22.251 PM
              2      20717 cdwjdd67x27mh      2979024279 12-MAY-14 03.11.22.188 PM
</pre>
<p>这里可以清晰看到，执行计划在1节点中发生震荡(两个执行计划都有选择)，仔细看两个执行计划，会发现就是查询的时候所使用的index不同而已,继续分析两个index</p>
<pre class="brush: sql; title: ; notranslate">
IDX_TAOBAO_BILL_CR_ISDP_S      CREATED_TIME                            1
IDX_TAOBAO_BILL_CR_ISDP_S      IS_DISPART                              2
IDX_TAOBAO_BILL_CR_ISDP_S      STATUS_ID                               3

IDX_TAOBAO_BILL_CR_REC_S       REC_SITE_ID                             1
IDX_TAOBAO_BILL_CR_REC_S       CREATED_TIME                            2
IDX_TAOBAO_BILL_CR_REC_S       STATUS_ID                               3
</pre>
<p>分析数据分布情况(其他列省略)</p>
<pre class="brush: sql; title: ; notranslate">
TABLE_NAME                     COLUMN_NAME                    NUM_DISTINCT LAST_ANAL
------------------------------ ------------------------------ ------------ ---------
GE_TAOBAO_BILL                 CREATED_TIME                      287080448 05-MAY-14
GE_TAOBAO_BILL                 REC_SITE_ID                           13176 05-MAY-14
GE_TAOBAO_BILL                 IS_DISPART                                2 05-MAY-14
GE_TAOBAO_BILL                 STATUS_ID                                 7 05-MAY-14
</pre>
<p>这里可以看到数据库在正常的时候使用IDX_TAOBAO_BILL_CR_REC_S没有问题，但是在某些情况下选择使用IDX_TAOBAO_BILL_CR_ISDP_S这个就有问题,导致逻辑读过高,其实对于该sql语句，是因为IDX_TAOBAO_BILL_CR_REC_S 索引不合理导致，如果创建CREATED_TIME,REC_SITE_ID,STATUS_ID，就不会因为传输的值范围不同而使用IDX_TAOBAO_BILL_CR_ISDP_S的情况。针对该情况，因为表非常大，短时间内无法修改index，只能考虑使用 sql profile固定执行计划<br />
<br />
<strong>sql profile固定计划</strong></p>
<pre class="brush: sql; title: ; notranslate">
SQL&gt;@coe_xfr_sql_profile.sql cdwjdd67x27mh

Parameter 1:
SQL_ID (required)



PLAN_HASH_VALUE AVG_ET_SECS
--------------- -----------
     2979024279        .011
      647855111       5.164

Parameter 2:
PLAN_HASH_VALUE (required)

Enter value for 2: 2979024279

Values passed:
~~~~~~~~~~~~~
SQL_ID         : &quot;cdwjdd67x27mh&quot;
PLAN_HASH_VALUE: &quot;2979024279&quot;


Execute coe_xfr_sql_profile_cdwjdd67x27mh_2979024279.sql
on TARGET system in order to create a custom SQL Profile
with plan 2979024279 linked to adjusted sql_text.


COE_XFR_SQL_PROFILE completed.
SQL&gt;@coe_xfr_sql_profile_cdwjdd67x27mh_2979024279.sql
SQL&gt;DECLARE
  2  sql_txt CLOB;
  3  h       SYS.SQLPROF_ATTR;
  4  BEGIN
  5  sql_txt := q'[
  6  select * from ( select
  7                  *
  8  
  9                  from
 10  
 11                  GE_TAOBAO_BILL
 12  
 13                  o
 14  
 15                   WHERE 1=1
 16  
 17  
 18  
 19  
 20  
 21  
 22  
 23  
 24  
 25  
 26  
 27                                  and o.CREATED_TIME &gt;= :1
 28  
 29  
 30                                  and o.CREATED_TIME &lt; :2
 31  
 32  
 33                                  and o.REC_SITE_ID = :3
 34  
 35  
 36  
 37  
 38  
 39  
 40  
 41  
 42  
 43  
 44  
 45  
 46  
 47  
 48  
 49                                  and o.STATUS_ID = :4
 50  
 51  
 52  
 53  
 54  
 55  
 56  
 57  
 58  
 59  
 60  
 61  
 62  
 63  
 64                                  and o.SERVICE_TYPE = :5 ) where rownum &lt;= 36000
 65  ]';
 66  h := SYS.SQLPROF_ATTR(
 67  q'[BEGIN_OUTLINE_DATA]',
 68  q'[IGNORE_OPTIM_EMBEDDED_HINTS]',
 69  q'[OPTIMIZER_FEATURES_ENABLE('11.2.0.3')]',
 70  q'[DB_VERSION('11.2.0.3')]',
 71  q'[FIRST_ROWS]',
 72  q'[OUTLINE_LEAF(@&quot;SEL$F5BB74E1&quot;)]',
 73  q'[MERGE(@&quot;SEL$2&quot;)]',
 74  q'[OUTLINE(@&quot;SEL$1&quot;)]',
 75  q'[OUTLINE(@&quot;SEL$2&quot;)]',
 76  q'[INDEX_RS_ASC(@&quot;SEL$F5BB74E1&quot; &quot;O&quot;@&quot;SEL$2&quot; (&quot;GE_TAOBAO_BILL&quot;.&quot;REC_SITE_ID&quot; &quot;GE_TAOBAO_BILL&quot;.&quot;CREATED_TIME&quot; &quot;GE_TAOBAO_BILL&quot;.&quot;STATUS_ID&quot;))]',
 77  q'[END_OUTLINE_DATA]');
 78  :signature := DBMS_SQLTUNE.SQLTEXT_TO_SIGNATURE(sql_txt);
 79  DBMS_SQLTUNE.IMPORT_SQL_PROFILE (
 80  sql_text    =&gt; sql_txt,
 81  profile     =&gt; h,
 82  name        =&gt; 'coe_cdwjdd67x27mh_2979024279',
 83  description =&gt; 'coe cdwjdd67x27mh 2979024279 '||:signature||'',
 84  category    =&gt; 'DEFAULT',
 85  validate    =&gt; TRUE,
 86  replace     =&gt; TRUE,
 87  force_match =&gt; FALSE /* TRUE:FORCE (match even when different literals in SQL). FALSE:EXACT (similar to CURSOR_SHARING) */ );
 88  END;
 89  /

PL/SQL procedure successfully completed.

SQL&gt;WHENEVER SQLERROR CONTINUE
SQL&gt;SET ECHO OFF;

            SIGNATURE
---------------------
 18414135509058398362


... manual custom SQL Profile has been created


COE_XFR_SQL_PROFILE_cdwjdd67x27mh_2979024279 completed
</pre>
<p>固定执行计划后，系统负载恢复正常<br />
load恢复正常，单个进程占用cpu 也正常</p>
<pre class="brush: sql; title: ; notranslate">
top - 18:25:29 up 123 days,  4:25,  3 users,  load average: 17.59, 16.72, 16.10
Tasks: 1559 total,   6 running, 1551 sleeping,   0 stopped,   2 zombie
Cpu(s):  6.2%us,  1.2%sy,  0.0%ni, 84.3%id,  7.4%wa,  0.1%hi,  0.9%si,  0.0%st
Mem:  264253752k total, 262395300k used,  1858452k free,   305928k buffers
Swap: 33554424k total,   467420k used, 33087004k free, 66811412k cached

  PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND                  
 3010 oracle    15   0  150g  26m  21m S 23.6  0.0   0:08.60 oracleq9db2 (LOCAL=NO)   
26936 oracle    15   0  150g  33m  28m S 22.9  0.0   0:12.53 oracleq9db2 (LOCAL=NO)   
 9691 oracle    15   0  150g  34m  28m D 21.0  0.0   0:48.73 oracleq9db2 (LOCAL=NO)   
 9694 oracle    15   0  150g  34m  28m S 17.4  0.0   0:45.74 oracleq9db2 (LOCAL=NO)   
14366 oracle    15   0  150g  33m  28m R 17.4  0.0   0:25.11 oracleq9db2 (LOCAL=NO)   
 2471 oracle    -2   0  150g 180m  37m S 16.7  0.1  10795:55 ora_lms3_q9db2           
 2463 oracle    -2   0  150g 180m  37m S 15.7  0.1  10648:38 ora_lms1_q9db2           
 2459 oracle    -2   0  150g 180m  37m S 14.8  0.1  10726:42 ora_lms0_q9db2           
 2467 oracle    -2   0  150g 180m  36m S 14.8  0.1  10980:33 ora_lms2_q9db2           
13324 oracle    15   0  150g  31m  26m S 14.1  0.0   0:22.75 oracleq9db2 (LOCAL=NO)   
16740 oracle    15   0  150g  34m  28m R 13.4  0.0   0:43.85 oracleq9db2 (LOCAL=NO)   
 1908 oracle    15   0  150g  27m  22m S 11.8  0.0   0:03.95 oracleq9db2 (LOCAL=NO)   
 9689 oracle    15   0  150g  33m  27m S 11.8  0.0   0:46.01 oracleq9db2 (LOCAL=NO)   
19410 oracle    15   0  150g  31m  26m S 11.8  0.0   0:43.18 oracleq9db2 (LOCAL=NO)   
14102 oracle    15   0  150g  31m  25m S 11.5  0.0   2:17.23 oracleq9db2 (LOCAL=NO)   
 1914 oracle    15   0  150g  29m  24m S 11.1  0.0   0:04.77 oracleq9db2 (LOCAL=NO)   
31106 oracle    15   0  150g  34m  28m S  9.8  0.0   1:24.85 oracleq9db2 (LOCAL=NO)   
31139 oracle    15   0  150g  30m  24m S  9.8  0.0   1:21.75 oracleq9db2 (LOCAL=NO)   
 2498 oracle    15   0  150g  42m  35m S  7.9  0.0   3838:43 ora_lgwr_q9db2           
28108 oracle    15   0  150g  36m  29m S  7.9  0.0   0:18.19 oracleq9db2 (LOCAL=NO)   
 2392 oracle    15   0  150g  35m  17m S  7.5  0.0   5304:57 ora_lmd0_q9db2           
</pre>
<div id="crp_related"><ul><li style="list-style-type:decimal;font-size:11px;" ><a href="https://www.xifenfei.com/2014/01/11-2-0-3-adg%e5%ba%93%e5%9b%a0-bug-16427872-%e5%af%bc%e8%87%b4smon%e5%8d%a0%e7%94%a8%e5%a4%a7%e9%87%8fcpu.html" rel="bookmark" class="crp_title">11.2.0.3 adg库因 bug 16427872 导致smon占用大量cpu</a></li><li style="list-style-type:decimal;font-size:11px;" ><a href="https://www.xifenfei.com/2012/05/sql-profile-%e4%bd%bf%e7%94%a8.html" rel="bookmark" class="crp_title">sql profile 使用</a></li><li style="list-style-type:decimal;font-size:11px;" ><a href="https://www.xifenfei.com/2018/01/reliable-message.html" rel="bookmark" class="crp_title">reliable message等待</a></li><li style="list-style-type:decimal;font-size:11px;" ><a href="https://www.xifenfei.com/2015/06/sql-profile%e6%94%b9%e5%8f%98hint%e7%9a%84%e6%89%a7%e8%a1%8c%e8%ae%a1%e5%88%92%e4%bb%a5%e5%8f%8acoe%e8%84%9a%e6%9c%ac%e5%ae%9e%e7%8e%b0sql-id%e4%b8%ad%e6%97%a0plan-hash-value%e7%9a%84sql-profile.html" rel="bookmark" class="crp_title">sql profile改变hint的执行计划以及coe脚本实现sql id中无PLAN HASH VALUE的sql profile生成</a></li><li style="list-style-type:decimal;font-size:11px;" ><a href="https://www.xifenfei.com/2013/08/oracle-12c-partial-globallocal-indexes-for-partitioned-tables.html" rel="bookmark" class="crp_title">ORACLE 12C Partial Global/Local Indexes for Partitioned Tables</a></li><li style="list-style-type:decimal;font-size:11px;" ><a href="https://www.xifenfei.com/2013/12/olr%e7%9b%b8%e5%85%b3%e7%bb%b4%e6%8a%a4.html" rel="bookmark" class="crp_title">OLR相关维护</a></li><li style="list-style-type:decimal;font-size:11px;" ><a href="https://www.xifenfei.com/2019/04/sql-plan-baseline.html" rel="bookmark" class="crp_title">sql plan baseline简单介绍</a></li><li style="list-style-type:decimal;font-size:11px;" ><a href="https://www.xifenfei.com/2014/06/oracle%e5%ae%89%e5%85%a8%e8%ad%a6%e7%a4%ba%e5%bd%95%e5%8a%a0%e9%94%99%e8%a3%b8%e8%ae%be%e5%a4%87%e5%af%bc%e8%87%b4redo%e5%bc%82%e5%b8%b8.html" rel="bookmark" class="crp_title">Oracle安全警示录:加错裸设备导致redo异常</a></li><li style="list-style-type:decimal;font-size:11px;" ><a href="https://www.xifenfei.com/2012/04/db2%e5%a4%87%e4%bb%bd%e6%81%a2%e5%a4%8d%e4%b8%8d%e5%ae%8c%e5%85%a8%e6%81%a2%e5%a4%8d.html" rel="bookmark" class="crp_title">DB2备份恢复(不完全恢复)</a></li><li style="list-style-type:decimal;font-size:11px;" ><a href="https://www.xifenfei.com/2012/07/cursor_sharingsimilar%e5%bc%95%e8%b5%b7%e7%9a%84%e6%82%b2%e5%89%a7.html" rel="bookmark" class="crp_title">CURSOR_SHARING=SIMILAR引起的悲剧</a></li><li style="list-style-type:decimal;font-size:11px;" ><a href="https://www.xifenfei.com/2012/05/cache-buffers-chains-latch%e7%ad%89%e5%be%85%e4%ba%8b%e4%bb%b6.html" rel="bookmark" class="crp_title">CACHE BUFFERS CHAINS等待事件</a></li><li style="list-style-type:decimal;font-size:11px;" ><a href="https://www.xifenfei.com/2012/05/cache-buffer-lru-chain-latch%e7%ad%89%e5%be%85%e4%ba%8b%e4%bb%b6.html" rel="bookmark" class="crp_title">cache buffer lru chain latch等待事件</a></li></ul></div>]]></content:encoded>
			<wfw:commentRss>https://www.xifenfei.com/2014/05/%e6%89%a7%e8%a1%8c%e8%ae%a1%e5%88%92%e6%94%b9%e5%8f%98%e5%af%bc%e8%87%b4%e6%95%b0%e6%8d%ae%e5%ba%93%e8%b4%9f%e8%bd%bd%e8%bf%87%e9%ab%98.html/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
