使用COE脚本绑定SQL Profile

日常运维中，经常会遇到需要绑定好的执行计划的场景。

简单来说，就是将一个sql_id绑定好的plan_hash_value。如果没有使用到绑定变量，还需要把froce_match设置为true。

用到的是MOS文档215187.1提供的系列脚本中的coe_xfr_sql_profile.sql。

下载地址：coe_xfr_sql_profile.sql.zip

脚本内容具体如下：

SPO coe_xfr_sql_profile.log;
SET DEF ON TERM OFF ECHO ON FEED OFF VER OFF HEA ON LIN 2000 PAGES 100 LONG 8000000 LONGC 800000 TRIMS ON TI OFF TIMI OFF SERVEROUT ON SIZE 1000000 NUMF "" SQLP SQL>;
SET SERVEROUT ON SIZE UNL;
REM
REM $Header: 215187.1 coe_xfr_sql_profile.sql 11.4.5.5 2013/03/01 carlos.sierra $
REM
REM Copyright (c) 2000-2013, Oracle Corporation. All rights reserved.
REM
REM AUTHOR
REM   carlos.sierra@oracle.com
REM
REM SCRIPT
REM   coe_xfr_sql_profile.sql
REM
REM DESCRIPTION
REM   This script generates another that contains the commands to
REM   create a manual custom SQL Profile out of a known plan from
REM   memory or AWR. The manual custom profile can be implemented
REM   into the same SOURCE system where the plan was retrieved,
REM   or into another similar TARGET system that has same schema
REM   objects referenced by the SQL that generated the known plan.
REM
REM PRE-REQUISITES
REM   1. Oracle Tuning Pack license.
REM
REM PARAMETERS
REM   1. SQL_ID (required)
REM   2. Plan Hash Value for which a manual custom SQL Profile is
REM      needed (required). A list of known plans is presented.
REM      You may choose from list provided or enter a valid phv
REM      from a version of the SQL modified with Hints.
REM
REM EXECUTION
REM   1. Connect into SQL*Plus as user with access to data dictionary.
REM      Do not use SYS.
REM   2. Execute script coe_xfr_sql_profile.sql passing SQL_ID and
REM      plan hash value (parameters can be passed inline or until
REM      requested).
REM
REM EXAMPLE
REM   # sqlplus system
REM   SQL> START coe_xfr_sql_profile.sql [SQL_ID] [PLAN_HASH_VALUE];
REM   SQL> START coe_xfr_sql_profile.sql gnjy0mn4y9pbm 2055843663;
REM   SQL> START coe_xfr_sql_profile.sql gnjy0mn4y9pbm;
REM   SQL> START coe_xfr_sql_profile.sql;
REM
REM NOTES
REM   1. For possible errors see coe_xfr_sql_profile.log
REM   2. If SQLT is installed in SOURCE, you can use instead:
REM      sqlt/utl/sqltprofile.sql
REM   3. Be aware that using DBMS_SQLTUNE requires a license for
REM      Oracle Tuning Pack.
REM   4. Use a DBA user but not SYS.
REM   5. If you get "ORA-06532: Subscript outside of limit, ORA-06512: at line 1"
REM      Then you may consider this change (only in a test and disposable system):
REM      create or replace TYPE sys.sqlprof_attr AS VARRAY(5000) of VARCHAR2(500);
REM
SET TERM ON ECHO OFF;
PRO
PRO Parameter 1:
PRO SQL_ID (required)
PRO
DEF sql_id = ‘&1‘;
PRO
WITH
p AS (
SELECT plan_hash_value
  FROM gv$sql_plan
 WHERE sql_id = TRIM(‘&&sql_id.‘)
   AND other_xml IS NOT NULL
 UNION
SELECT plan_hash_value
  FROM dba_hist_sql_plan
 WHERE sql_id = TRIM(‘&&sql_id.‘)
   AND other_xml IS NOT NULL ),
m AS (
SELECT plan_hash_value,
       SUM(elapsed_time)/SUM(executions) avg_et_secs
  FROM gv$sql
 WHERE sql_id = TRIM(‘&&sql_id.‘)
   AND executions > 0
 GROUP BY
       plan_hash_value ),
a AS (
SELECT plan_hash_value,
       SUM(elapsed_time_total)/SUM(executions_total) avg_et_secs
  FROM dba_hist_sqlstat
 WHERE sql_id = TRIM(‘&&sql_id.‘)
   AND executions_total > 0
 GROUP BY
       plan_hash_value )
SELECT p.plan_hash_value,
       ROUND(NVL(m.avg_et_secs, a.avg_et_secs)/1e6, 3) avg_et_secs
  FROM p, m, a
 WHERE p.plan_hash_value = m.plan_hash_value(+)
   AND p.plan_hash_value = a.plan_hash_value(+)
 ORDER BY
       avg_et_secs NULLS LAST;
PRO
PRO Parameter 2:
PRO PLAN_HASH_VALUE (required)
PRO
DEF plan_hash_value = ‘&2‘;
PRO
PRO Values passed to coe_xfr_sql_profile:
PRO ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
PRO SQL_ID         : "&&sql_id."
PRO PLAN_HASH_VALUE: "&&plan_hash_value."
PRO
SET TERM OFF ECHO ON;
WHENEVER SQLERROR EXIT SQL.SQLCODE;

-- trim parameters
COL sql_id NEW_V sql_id FOR A30;
COL plan_hash_value NEW_V plan_hash_value FOR A30;
SELECT TRIM(‘&&sql_id.‘) sql_id, TRIM(‘&&plan_hash_value.‘) plan_hash_value FROM DUAL;

VAR sql_text CLOB;
VAR sql_text2 CLOB;
VAR other_xml CLOB;
EXEC :sql_text := NULL;
EXEC :sql_text2 := NULL;
EXEC :other_xml := NULL;

-- get sql_text from memory
DECLARE
  l_sql_text VARCHAR2(32767);
BEGIN -- 10g see bug 5017909
  FOR i IN (SELECT DISTINCT piece, sql_text
              FROM gv$sqltext_with_newlines
             WHERE sql_id = TRIM(‘&&sql_id.‘)
             ORDER BY 1, 2)
  LOOP
    IF :sql_text IS NULL THEN
      DBMS_LOB.CREATETEMPORARY(:sql_text, TRUE);
      DBMS_LOB.OPEN(:sql_text, DBMS_LOB.LOB_READWRITE);
    END IF;
    -- removes NUL characters
    l_sql_text := REPLACE(i.sql_text, CHR(00), ‘ ‘);
    -- adds a NUL character at the end of each line
    DBMS_LOB.WRITEAPPEND(:sql_text, LENGTH(l_sql_text) + 1, l_sql_text||CHR(00));
  END LOOP;
  -- if found in memory then sql_text is not null
  IF :sql_text IS NOT NULL THEN
    DBMS_LOB.CLOSE(:sql_text);
  END IF;
EXCEPTION
  WHEN OTHERS THEN
    DBMS_OUTPUT.PUT_LINE(‘getting sql_text from memory: ‘||SQLERRM);
    :sql_text := NULL;
END;
/

SELECT :sql_text FROM DUAL;

-- get sql_text from awr
DECLARE
  l_sql_text VARCHAR2(32767);
  l_clob_size NUMBER;
  l_offset NUMBER;
BEGIN
  IF :sql_text IS NULL OR NVL(DBMS_LOB.GETLENGTH(:sql_text), 0) = 0 THEN
    SELECT sql_text
      INTO :sql_text2
      FROM dba_hist_sqltext
     WHERE sql_id = TRIM(‘&&sql_id.‘)
       AND sql_text IS NOT NULL
       AND ROWNUM = 1;
  END IF;
  -- if found in awr then sql_text2 is not null
  IF :sql_text2 IS NOT NULL THEN
    l_clob_size := NVL(DBMS_LOB.GETLENGTH(:sql_text2), 0);
    l_offset := 1;
    DBMS_LOB.CREATETEMPORARY(:sql_text, TRUE);
    DBMS_LOB.OPEN(:sql_text, DBMS_LOB.LOB_READWRITE);
    -- store in clob as 64 character pieces plus a NUL character at the end of each piece
    WHILE l_offset < l_clob_size
    LOOP
      IF l_clob_size - l_offset > 64 THEN
        l_sql_text := REPLACE(DBMS_LOB.SUBSTR(:sql_text2, 64, l_offset), CHR(00), ‘ ‘);
      ELSE -- last piece
        l_sql_text := REPLACE(DBMS_LOB.SUBSTR(:sql_text2, l_clob_size - l_offset + 1, l_offset), CHR(00), ‘ ‘);
      END IF;
      DBMS_LOB.WRITEAPPEND(:sql_text, LENGTH(l_sql_text) + 1, l_sql_text||CHR(00));
      l_offset := l_offset + 64;
    END LOOP;
    DBMS_LOB.CLOSE(:sql_text);
  END IF;
EXCEPTION
  WHEN OTHERS THEN
    DBMS_OUTPUT.PUT_LINE(‘getting sql_text from awr: ‘||SQLERRM);
    :sql_text := NULL;
END;
/

SELECT :sql_text2 FROM DUAL;
SELECT :sql_text FROM DUAL;

-- validate sql_text
SET TERM ON;
BEGIN
  IF :sql_text IS NULL THEN
    RAISE_APPLICATION_ERROR(-20100, ‘SQL_TEXT for SQL_ID &&sql_id. was not found in memory (gv$sqltext_with_newlines) or AWR (dba_hist_sqltext).‘);
  END IF;
END;
/
SET TERM OFF;

-- get other_xml from memory
BEGIN
  FOR i IN (SELECT other_xml
              FROM gv$sql_plan
             WHERE sql_id = TRIM(‘&&sql_id.‘)
               AND plan_hash_value = TO_NUMBER(TRIM(‘&&plan_hash_value.‘))
               AND other_xml IS NOT NULL
             ORDER BY
                   child_number, id)
  LOOP
    :other_xml := i.other_xml;
    EXIT; -- 1st
  END LOOP;
EXCEPTION
  WHEN OTHERS THEN
    DBMS_OUTPUT.PUT_LINE(‘getting other_xml from memory: ‘||SQLERRM);
    :other_xml := NULL;
END;
/

-- get other_xml from awr
BEGIN
  IF :other_xml IS NULL OR NVL(DBMS_LOB.GETLENGTH(:other_xml), 0) = 0 THEN
    FOR i IN (SELECT other_xml
                FROM dba_hist_sql_plan
               WHERE sql_id = TRIM(‘&&sql_id.‘)
                 AND plan_hash_value = TO_NUMBER(TRIM(‘&&plan_hash_value.‘))
                 AND other_xml IS NOT NULL
               ORDER BY
                     id)
    LOOP
      :other_xml := i.other_xml;
      EXIT; -- 1st
    END LOOP;
  END IF;
EXCEPTION
  WHEN OTHERS THEN
    DBMS_OUTPUT.PUT_LINE(‘getting other_xml from awr: ‘||SQLERRM);
    :other_xml := NULL;
END;
/

-- get other_xml from memory from modified SQL
BEGIN
  IF :other_xml IS NULL OR NVL(DBMS_LOB.GETLENGTH(:other_xml), 0) = 0 THEN
    FOR i IN (SELECT other_xml
                FROM gv$sql_plan
               WHERE plan_hash_value = TO_NUMBER(TRIM(‘&&plan_hash_value.‘))
                 AND other_xml IS NOT NULL
               ORDER BY
                     child_number, id)
    LOOP
      :other_xml := i.other_xml;
      EXIT; -- 1st
    END LOOP;
  END IF;
EXCEPTION
  WHEN OTHERS THEN
    DBMS_OUTPUT.PUT_LINE(‘getting other_xml from memory: ‘||SQLERRM);
    :other_xml := NULL;
END;
/

-- get other_xml from awr from modified SQL
BEGIN
  IF :other_xml IS NULL OR NVL(DBMS_LOB.GETLENGTH(:other_xml), 0) = 0 THEN
    FOR i IN (SELECT other_xml
                FROM dba_hist_sql_plan
               WHERE plan_hash_value = TO_NUMBER(TRIM(‘&&plan_hash_value.‘))
                 AND other_xml IS NOT NULL
               ORDER BY
                     id)
    LOOP
      :other_xml := i.other_xml;
      EXIT; -- 1st
    END LOOP;
  END IF;
EXCEPTION
  WHEN OTHERS THEN
    DBMS_OUTPUT.PUT_LINE(‘getting other_xml from awr: ‘||SQLERRM);
    :other_xml := NULL;
END;
/

SELECT :other_xml FROM DUAL;

-- validate other_xml
SET TERM ON;
BEGIN
  IF :other_xml IS NULL THEN
    RAISE_APPLICATION_ERROR(-20101, ‘PLAN for SQL_ID &&sql_id. and PHV &&plan_hash_value. was not found in memory (gv$sql_plan) or AWR (dba_hist_sql_plan).‘);
  END IF;
END;
/
SET TERM OFF;

-- generates script that creates sql profile in target system:
SET ECHO OFF;
PRO coe_xfr_sql_profile_&&sql_id._&&plan_hash_value..sql.
SET FEED OFF LIN 666 TRIMS ON TI OFF TIMI OFF SERVEROUT ON SIZE 1000000 FOR WOR;
SET SERVEROUT ON SIZE UNL FOR WOR;
SPO OFF;
SPO coe_xfr_sql_profile_&&sql_id._&&plan_hash_value..sql;
DECLARE
  l_pos NUMBER;
  l_clob_size NUMBER;
  l_offset NUMBER;
  l_sql_text VARCHAR2(32767);
  l_len NUMBER;
  l_hint VARCHAR2(32767);
BEGIN
  DBMS_OUTPUT.PUT_LINE(‘SPO coe_xfr_sql_profile_&&sql_id._&&plan_hash_value..log;‘);
  DBMS_OUTPUT.PUT_LINE(‘SET ECHO ON TERM ON LIN 2000 TRIMS ON NUMF 99999999999999999999;‘);
  DBMS_OUTPUT.PUT_LINE(‘REM‘);
  DBMS_OUTPUT.PUT_LINE(‘REM $Header: 215187.1 coe_xfr_sql_profile_&&sql_id._&&plan_hash_value..sql 11.4.4.4 ‘||TO_CHAR(SYSDATE, ‘YYYY/MM/DD‘)||‘ carlos.sierra $‘);
  DBMS_OUTPUT.PUT_LINE(‘REM‘);
  DBMS_OUTPUT.PUT_LINE(‘REM Copyright (c) 2000-2012, Oracle Corporation. All rights reserved.‘);
  DBMS_OUTPUT.PUT_LINE(‘REM‘);
  DBMS_OUTPUT.PUT_LINE(‘REM AUTHOR‘);
  DBMS_OUTPUT.PUT_LINE(‘REM   [email protected]‘);
  DBMS_OUTPUT.PUT_LINE(‘REM‘);
  DBMS_OUTPUT.PUT_LINE(‘REM SCRIPT‘);
  DBMS_OUTPUT.PUT_LINE(‘REM   coe_xfr_sql_profile_&&sql_id._&&plan_hash_value..sql‘);
  DBMS_OUTPUT.PUT_LINE(‘REM‘);
  DBMS_OUTPUT.PUT_LINE(‘REM DESCRIPTION‘);
  DBMS_OUTPUT.PUT_LINE(‘REM   This script is generated by coe_xfr_sql_profile.sql‘);
  DBMS_OUTPUT.PUT_LINE(‘REM   It contains the SQL*Plus commands to create a custom‘);
  DBMS_OUTPUT.PUT_LINE(‘REM   SQL Profile for SQL_ID &&sql_id. based on plan hash‘);
  DBMS_OUTPUT.PUT_LINE(‘REM   value &&plan_hash_value..‘);
  DBMS_OUTPUT.PUT_LINE(‘REM   The custom SQL Profile to be created by this script‘);
  DBMS_OUTPUT.PUT_LINE(‘REM   will affect plans for SQL commands with signature‘);
  DBMS_OUTPUT.PUT_LINE(‘REM   matching the one for SQL Text below.‘);
  DBMS_OUTPUT.PUT_LINE(‘REM   Review SQL Text and adjust accordingly.‘);
  DBMS_OUTPUT.PUT_LINE(‘REM‘);
  DBMS_OUTPUT.PUT_LINE(‘REM PARAMETERS‘);
  DBMS_OUTPUT.PUT_LINE(‘REM   None.‘);
  DBMS_OUTPUT.PUT_LINE(‘REM‘);
  DBMS_OUTPUT.PUT_LINE(‘REM EXAMPLE‘);
  DBMS_OUTPUT.PUT_LINE(‘REM   SQL> START coe_xfr_sql_profile_&&sql_id._&&plan_hash_value..sql;‘);
  DBMS_OUTPUT.PUT_LINE(‘REM‘);
  DBMS_OUTPUT.PUT_LINE(‘REM NOTES‘);
  DBMS_OUTPUT.PUT_LINE(‘REM   1. Should be run as SYSTEM or SYSDBA.‘);
  DBMS_OUTPUT.PUT_LINE(‘REM   2. User must have CREATE ANY SQL PROFILE privilege.‘);
  DBMS_OUTPUT.PUT_LINE(‘REM   3. SOURCE and TARGET systems can be the same or similar.‘);
  DBMS_OUTPUT.PUT_LINE(‘REM   4. To drop this custom SQL Profile after it has been created:‘);
  DBMS_OUTPUT.PUT_LINE(‘REM      EXEC DBMS_SQLTUNE.DROP_SQL_PROFILE(‘‘coe_&&sql_id._&&plan_hash_value.‘‘);‘);
  DBMS_OUTPUT.PUT_LINE(‘REM   5. Be aware that using DBMS_SQLTUNE requires a license‘);
  DBMS_OUTPUT.PUT_LINE(‘REM      for the Oracle Tuning Pack.‘);
  DBMS_OUTPUT.PUT_LINE(‘REM   6. If you modified a SQL putting Hints in order to produce a desired‘);
  DBMS_OUTPUT.PUT_LINE(‘REM      Plan, you can remove the artifical Hints from SQL Text pieces below.‘);
  DBMS_OUTPUT.PUT_LINE(‘REM      By doing so you can create a custom SQL Profile for the original‘);
  DBMS_OUTPUT.PUT_LINE(‘REM      SQL but with the Plan captured from the modified SQL (with Hints).‘);
  DBMS_OUTPUT.PUT_LINE(‘REM‘);
  DBMS_OUTPUT.PUT_LINE(‘WHENEVER SQLERROR EXIT SQL.SQLCODE;‘);
  DBMS_OUTPUT.PUT_LINE(‘REM‘);
  DBMS_OUTPUT.PUT_LINE(‘VAR signature NUMBER;‘);
  DBMS_OUTPUT.PUT_LINE(‘VAR signaturef NUMBER;‘);
  DBMS_OUTPUT.PUT_LINE(‘REM‘);
  DBMS_OUTPUT.PUT_LINE(‘DECLARE‘);
  DBMS_OUTPUT.PUT_LINE(‘sql_txt CLOB;‘);
  DBMS_OUTPUT.PUT_LINE(‘h       SYS.SQLPROF_ATTR;‘);
  DBMS_OUTPUT.PUT_LINE(‘PROCEDURE wa (p_line IN VARCHAR2) IS‘);
  DBMS_OUTPUT.PUT_LINE(‘BEGIN‘);
  DBMS_OUTPUT.PUT_LINE(‘DBMS_LOB.WRITEAPPEND(sql_txt, LENGTH(p_line), p_line);‘);
  DBMS_OUTPUT.PUT_LINE(‘END wa;‘);
  DBMS_OUTPUT.PUT_LINE(‘BEGIN‘);
  DBMS_OUTPUT.PUT_LINE(‘DBMS_LOB.CREATETEMPORARY(sql_txt, TRUE);‘);
  DBMS_OUTPUT.PUT_LINE(‘DBMS_LOB.OPEN(sql_txt, DBMS_LOB.LOB_READWRITE);‘);
  DBMS_OUTPUT.PUT_LINE(‘-- SQL Text pieces below do not have to be of same length.‘);
  DBMS_OUTPUT.PUT_LINE(‘-- So if you edit SQL Text (i.e. removing temporary Hints),‘);
  DBMS_OUTPUT.PUT_LINE(‘-- there is no need to edit or re-align unmodified pieces.‘);
  l_clob_size := NVL(DBMS_LOB.GETLENGTH(:sql_text), 0);
  l_offset := 1;
  WHILE l_offset < l_clob_size
  LOOP
    l_pos := DBMS_LOB.INSTR(:sql_text, CHR(00), l_offset);
    IF l_pos > 0 THEN
      l_len := l_pos - l_offset;
    ELSE -- last piece
      l_len := l_clob_size - l_pos + 1;
    END IF;
    l_sql_text := DBMS_LOB.SUBSTR(:sql_text, l_len, l_offset);
    /* cannot do such 3 replacement since a line could end with a comment using "--"
    l_sql_text := REPLACE(l_sql_text, CHR(10), ‘ ‘); -- replace LF with SP
    l_sql_text := REPLACE(l_sql_text, CHR(13), ‘ ‘); -- replace CR with SP
    l_sql_text := REPLACE(l_sql_text, CHR(09), ‘ ‘); -- replace TAB with SP
    */
    l_offset := l_offset + l_len + 1;
    IF l_len > 0 THEN
      IF INSTR(l_sql_text, ‘‘‘[‘) + INSTR(l_sql_text, ‘]‘‘‘) = 0 THEN
        l_sql_text := ‘[‘||l_sql_text||‘]‘;
      ELSIF INSTR(l_sql_text, ‘‘‘{‘) + INSTR(l_sql_text, ‘}‘‘‘) = 0 THEN
        l_sql_text := ‘{‘||l_sql_text||‘}‘;
      ELSIF INSTR(l_sql_text, ‘‘‘<‘) + INSTR(l_sql_text, ‘>‘‘‘) = 0 THEN
        l_sql_text := ‘<‘||l_sql_text||‘>‘;
      ELSIF INSTR(l_sql_text, ‘‘‘(‘) + INSTR(l_sql_text, ‘)‘‘‘) = 0 THEN
        l_sql_text := ‘(‘||l_sql_text||‘)‘;
      ELSIF INSTR(l_sql_text, ‘‘‘"‘) + INSTR(l_sql_text, ‘"‘‘‘) = 0 THEN
        l_sql_text := ‘"‘||l_sql_text||‘"‘;
      ELSIF INSTR(l_sql_text, ‘‘‘|‘) + INSTR(l_sql_text, ‘|‘‘‘) = 0 THEN
        l_sql_text := ‘|‘||l_sql_text||‘|‘;
      ELSIF INSTR(l_sql_text, ‘‘‘~‘) + INSTR(l_sql_text, ‘~‘‘‘) = 0 THEN
        l_sql_text := ‘~‘||l_sql_text||‘~‘;
      ELSIF INSTR(l_sql_text, ‘‘‘^‘) + INSTR(l_sql_text, ‘^‘‘‘) = 0 THEN
        l_sql_text := ‘^‘||l_sql_text||‘^‘;
      ELSIF INSTR(l_sql_text, ‘‘‘@‘) + INSTR(l_sql_text, ‘@‘‘‘) = 0 THEN
        l_sql_text := ‘@‘||l_sql_text||‘@‘;
      ELSIF INSTR(l_sql_text, ‘‘‘#‘) + INSTR(l_sql_text, ‘#‘‘‘) = 0 THEN
        l_sql_text := ‘#‘||l_sql_text||‘#‘;
      ELSIF INSTR(l_sql_text, ‘‘‘%‘) + INSTR(l_sql_text, ‘%‘‘‘) = 0 THEN
        l_sql_text := ‘%‘||l_sql_text||‘%‘;
      ELSIF INSTR(l_sql_text, ‘‘‘$‘) + INSTR(l_sql_text, ‘$‘‘‘) = 0 THEN
        l_sql_text := ‘$‘||l_sql_text||‘$‘;
      ELSE
        l_sql_text := CHR(96)||l_sql_text||CHR(96);
      END IF;
      DBMS_OUTPUT.PUT_LINE(‘wa(q‘‘‘||l_sql_text||‘‘‘);‘);
    END IF;
  END LOOP;
  DBMS_OUTPUT.PUT_LINE(‘DBMS_LOB.CLOSE(sql_txt);‘);
  DBMS_OUTPUT.PUT_LINE(‘h := SYS.SQLPROF_ATTR(‘);
  DBMS_OUTPUT.PUT_LINE(‘q‘‘[BEGIN_OUTLINE_DATA]‘‘,‘);
  FOR i IN (SELECT /*+ opt_param(‘parallel_execution_enabled‘, ‘false‘) */
                   SUBSTR(EXTRACTVALUE(VALUE(d), ‘/hint‘), 1, 4000) hint
              FROM TABLE(XMLSEQUENCE(EXTRACT(XMLTYPE(:other_xml), ‘/*/outline_data/hint‘))) d)
  LOOP
    l_hint := i.hint;
    WHILE NVL(LENGTH(l_hint), 0) > 0
    LOOP
      IF LENGTH(l_hint) <= 500 THEN
        DBMS_OUTPUT.PUT_LINE(‘q‘‘[‘||l_hint||‘]‘‘,‘);
        l_hint := NULL;
      ELSE
        l_pos := INSTR(SUBSTR(l_hint, 1, 500), ‘ ‘, -1);
        DBMS_OUTPUT.PUT_LINE(‘q‘‘[‘||SUBSTR(l_hint, 1, l_pos)||‘]‘‘,‘);
        l_hint := ‘   ‘||SUBSTR(l_hint, l_pos);
      END IF;
    END LOOP;
  END LOOP;
  DBMS_OUTPUT.PUT_LINE(‘q‘‘[END_OUTLINE_DATA]‘‘);‘);
  DBMS_OUTPUT.PUT_LINE(‘:signature := DBMS_SQLTUNE.SQLTEXT_TO_SIGNATURE(sql_txt);‘);
  DBMS_OUTPUT.PUT_LINE(‘:signaturef := DBMS_SQLTUNE.SQLTEXT_TO_SIGNATURE(sql_txt, TRUE);‘);
  DBMS_OUTPUT.PUT_LINE(‘DBMS_SQLTUNE.IMPORT_SQL_PROFILE (‘);
  DBMS_OUTPUT.PUT_LINE(‘sql_text    => sql_txt,‘);
  DBMS_OUTPUT.PUT_LINE(‘profile     => h,‘);
  DBMS_OUTPUT.PUT_LINE(‘name        => ‘‘coe_&&sql_id._&&plan_hash_value.‘‘,‘);
  DBMS_OUTPUT.PUT_LINE(‘description => ‘‘coe &&sql_id. &&plan_hash_value. ‘‘||:signature||‘‘ ‘‘||:signaturef||‘‘‘‘,‘);
  DBMS_OUTPUT.PUT_LINE(‘category    => ‘‘DEFAULT‘‘,‘);
  DBMS_OUTPUT.PUT_LINE(‘validate    => TRUE,‘);
  DBMS_OUTPUT.PUT_LINE(‘replace     => TRUE,‘);
  DBMS_OUTPUT.PUT_LINE(‘force_match => FALSE /* TRUE:FORCE (match even when different literals in SQL). FALSE:EXACT (similar to CURSOR_SHARING) */ );‘);
  DBMS_OUTPUT.PUT_LINE(‘DBMS_LOB.FREETEMPORARY(sql_txt);‘);
  DBMS_OUTPUT.PUT_LINE(‘END;‘);
  DBMS_OUTPUT.PUT_LINE(‘/‘);
  DBMS_OUTPUT.PUT_LINE(‘WHENEVER SQLERROR CONTINUE‘);
  DBMS_OUTPUT.PUT_LINE(‘SET ECHO OFF;‘);
  DBMS_OUTPUT.PUT_LINE(‘PRINT signature‘);
  DBMS_OUTPUT.PUT_LINE(‘PRINT signaturef‘);
  DBMS_OUTPUT.PUT_LINE(‘PRO‘);
  DBMS_OUTPUT.PUT_LINE(‘PRO ... manual custom SQL Profile has been created‘);
  DBMS_OUTPUT.PUT_LINE(‘PRO‘);
  DBMS_OUTPUT.PUT_LINE(‘SET TERM ON ECHO OFF LIN 80 TRIMS OFF NUMF "";‘);
  DBMS_OUTPUT.PUT_LINE(‘SPO OFF;‘);
  DBMS_OUTPUT.PUT_LINE(‘PRO‘);
  DBMS_OUTPUT.PUT_LINE(‘PRO COE_XFR_SQL_PROFILE_&&sql_id._&&plan_hash_value. completed‘);
END;
/
SPO OFF;
SET DEF ON TERM ON ECHO OFF FEED 6 VER ON HEA ON LIN 80 PAGES 14 LONG 80 LONGC 80 TRIMS OFF TI OFF TIMI OFF SERVEROUT OFF NUMF "" SQLP SQL>;
SET SERVEROUT OFF;
PRO
PRO Execute coe_xfr_sql_profile_&&sql_id._&&plan_hash_value..sql
PRO on TARGET system in order to create a custom SQL Profile
PRO with plan &&plan_hash_value linked to adjusted sql_text.
PRO
UNDEFINE 1 2 sql_id plan_hash_value
CL COL
PRO
PRO COE_XFR_SQL_PROFILE completed.

原文地址：https://www.cnblogs.com/jyzhao/p/9256293.html

时间： 2024-09-27 20:15:37

使用COE脚本绑定SQL Profile的相关文章

SQLT导入测试数据，及SQL Profile的使用

性能分析过程中,经常会遇到生产库出现SQL的性能问题,但是,我们没有办法在生产库上做很多动作,需要将这个SQL的对应的表结构信息,统计信息导入到测试库进行测试(没有真实的测试数据,只有统计信息) 本次测试目的,客户环境导出了Test和product环境的相同SQL的不同执行计划的SQLT报告. TEST环境是11.2.0.1版本 Product是11.2.0.2版本 我们会将两个SQLT报告分别导入到11.2.0.1和11.2.0.2的测试环境中,然后将11.2.0.1版本,好的执行计划,作为p

Oracle固定SQL的执行计划(一)---SQL Profile

我们都希望对于所有在Oracle数据库中执行的SQL,CBO都能产生出正确的执行计划,但实际情况却并非如此,由于各种各样的原因(比如目标SQL所涉及的对象的统计信息的不准确,或者CBO内部一些成本计算公式的先天缺陷等),导致有时CBO产生效率不高.甚至是错误的执行计划.特别是CBO对目标SQL所产生的初始执行计划是正确的,后来由于某种原因(比如统计信息的变更等)而导致CBO重新对其产生了错误的执行计划,这种执行计划的改变往往会导致目标SQL执行时间呈数量级的递增,而且常常会让我们很困惑:这个SQ

SQL Profile 如何使用

这些文章是我从<基于Oracle的SQL优化> 书中找到的 可以参考一下我的实验过程 SQL Profile Oracle10G中的SQL Profile可以说是Oracle 9i中的Stored Outline的进化. Stored Outline能够实现的功能SQL Profile也完全能够实现. 与Stored Outline相比,SQL Profile具备如下优点: 更容易生成.更改和控制. 在对SQL语句的支持上做得更好,也就是说适用范围更广. 使用SQL Profile可以容易实现

Oracle 通过sql profile为sql语句加hint

sql profile最大的优点是在不修改sql语句和会话执行环境的情况下去优化sql的执行效率,适合无法在应用程序中修改sql时.sql profile最常用方法大概是:--创建产生sql tuning advisor任务DECLARE  tuning_task varchar2(100);  l_sql_id    v$session.prev_sql_id%TYPE;BEGIN  l_sql_id    := '6w02d3ggsj4xb';  tuning_task := dbms_sq

SQL Profile 总结（四）--使用示例

前提:sql profile工具的相关视图 dba_sql_profile 10g: sys.sqlprof$attr  &  sqlprof$ 11g: sys.sqlobj$data  &  sys.sqlobj$ 1.主要完成四个示例,如下 使用dbms_sqltune.import_sql_profile过程手工指定提示的方式,这种方式要求非常高(查询块名等),一般不会使用 使用create_sql_profile.sql脚本固定内存中已经有的SQL的执行计划,通过指定sql_id

使用SQL Profile及SQL Tuning Advisor固定执行计划

SQL Profile就是为某一SQL语句提供除了系统统计信息.对象(表和索引等)统计信息之外的其他信息,比如运行环境.额外的更准确的统计信息,以帮助优化器为SQL语句选择更适合的执行计划. SQL Profiles可以说是Outlines的进化.Outlines能够实现的功能SQL Profiles也完全能够实现,而SQL Profiles具有Outlines不具备的优化,最重要的有二点: SQL Profiles更容易生成.更改和控制. SQL Profiles在对SQL语句的支持上做得更好

MSSQL-Scripter，一个新的生成T-SQL脚本的SQL Server命令行工具

这里向大家介绍一个新的生成T-SQL脚本的SQL Server命令行工具:mssql-scripter.它支持在SQL Server.Azure SQL DB以及Azure SQL DW中为数据库生成CREATE和INSERT T-SQL脚本. Mssql-scripter是一个跨平台的命令行工具,功能等同于SQL Server Management Studio中的Generate and Publish Scripts Wizard. 咱们能够在Linux.macOS和Windows上使用它

Spring JDBC 框架中, 绑定 SQL 参数的另一种选择：具名参数(named parameter)

使用spring的jdbcTemplate-----使用具名参数 在JDBC用法中,SQL参数是用占位符?表示,并且受到位置的限制,定位参数的问题在于,一旦参数的位置发生变化,必须改变参数的绑定,在Spring JDBC中,绑定SQL参数的另一种选择是使用具名参数,SQL具名参数是按照名称绑定,而不是位置绑定. 什么是具名参数? 具名参数: SQL 按名称(以冒号开头)而不是按位置进行指定. 具名参数更易于维护, 也提升了可读性. 具名参数由框架类在运行时用占位符取代 具名参数只在 NamedP

SQL Profile 总结（一）

一.前提概述 在介绍SQL Profile之前,不得不说的一个工具就是SQL Tuning Advisor:这个工具是从Oracle 10g開始引入,它的任务就是分析一个指定的SQL语句,并建议怎样使用一些方法来提高指定语句的性能,比如:收集缺失的对象统计信息.或者收集过时的对象统计信息.创建新的索引.调整SQL语句结构.採用SQL Profile等等方式. 二.为什么SQL Tuning Advisor可以找出提高语句性能的方法? 这须要从SQL Tuning Advisor的工作原理開始说明