{ "date": "2015-05-18T13:17:21", "slug": "matching-sql-plan-directives-and-queries-using-it", "link": "https://www.dbi-services.com/blog/matching-sql-plan-directives-and-queries-using-it/", "title": { "rendered": "Matching SQL Plan Directives and queries using it" }, "content": { "rendered": "

By Franck Pachot

\n

.
\nThis is another blog post I’m writing while reviewing the presentation I’m doing next week forSOUG and next month for DOAG. You have SQL Plan Directives used by several queries that have same kind of predicates. And queries that can use several SPD. Can you match them?

\n

When a query uses a SPD (meaning that the SPD in usable state – NEW, MISSING_STATS or PERMANENT internal state) the execution plan show it as:

\n
Note\n-----\n   - dynamic statistics used: dynamic sampling (level=2)\n   - 1 Sql Plan Directive used for this statement\n
\n

but you don’t have information about which directive(s).

\n

Unfortunately that information is not stored in V$SQL_PLAN information. There are two ways to get information:

\n\n

example

\n

Here are the SQL Plan Directives I have:

\n
SQL> select directive_id,type,state,reason,notes,created,last_modified,last_used from dba_sql_plan_d\nirectives where directive_id in( select directive_id from dba_sql_plan_dir_objects where owner='DEMO\n' ) order by created;\n\n           DIRECTIVE_ID TYPE             STATE      REASON\n----------------------- ---------------- ---------- ------------------------------------\nNOTES                                                                                      CREATED\n------------------------------------------------------------------------------------------ --------\nLAST_MOD LAST_USE\n-------- --------\n   11092019653200552215 DYNAMIC_SAMPLING SUPERSEDED SINGLE TABLE CARDINALITY MISESTIMATE\n.spd_note.                                                                                 21:21:58\n  .internal_state.HAS_STATS./internal_state.\n  .redundant.NO./redundant.\n  .spd_text.{EC(DEMO.DEMO_TABLE)[A, B, C, D]}./spd_text.\n./spd_note.\n21:30:09 21:30:09\n\n    9695481911885124390 DYNAMIC_SAMPLING USABLE     SINGLE TABLE CARDINALITY MISESTIMATE\n.spd_note.                                                                                 21:35:45\n  .internal_state.NEW./internal_state.\n  .redundant.NO./redundant.\n  .spd_text.{E(DEMO.DEMO_TABLE)[A, B, C, D]}./spd_text.\n./spd_note.\n
\n

(I changed the xml tag because our current blog platform is a bit creative with them… fortunately we are migrating soon to wordpress)

\n

+metrics

\n

So in order to have more information, you have to re-parse the statement with EXPLAIN PLAN FOR… and show it with DBMS_XPLAN.DISPLAY witht he format ‘+METRICS’

\n
SQL> explain plan for select * from DEMO_TABLE where a+b=c+d;\n\nExplained.\n
\n

This query will use the {E(DEMO.DEMO_TABLE)[A, B, C, D]} directive but not the {EC(DEMO.DEMO_TABLE)[A, B, C, D]} one because it’s not simple columns predicates.
\nLet’s get the execution plan from PLAN_TABLE with the +METRICS format:

\n
SQL> select * from table(dbms_xplan.display(null,null,'+metrics'));\n\nPLAN_TABLE_OUTPUT\n----------------------------------------------------------------------------------------------------\nPlan hash value: 4063024151\n\n--------------------------------------------------------------------------------\n| Id  | Operation         | Name       | Rows  | Bytes | Cost (%CPU)| Time     |\n--------------------------------------------------------------------------------\n|   0 | SELECT STATEMENT  |            |  1000 | 12000 |     3   (0)| 00:00:01 |\n|*  1 |  TABLE ACCESS FULL| DEMO_TABLE |  1000 | 12000 |     3   (0)| 00:00:01 |\n--------------------------------------------------------------------------------\n\nPredicate Information (identified by operation id):\n---------------------------------------------------\n\n   1 - filter(\"A\"+\"B\"=\"C\"+\"D\")\n\nSql Plan Directive information:\n-------------------------------\n\n  Used directive ids:\n    9695481911885124390\n\nNote\n-----\n   - dynamic statistics used: dynamic sampling (level=2)\n   - 1 Sql Plan Directive used for this statement\n\n
\n

As you can see, in addition to the number of SPD used you have the DIRECTIVE ID.

\n

Conclusion

\n

It’s not easy to match all queries that can use a SQL Plan Directive, but you can do it on the other way: do an explain plan for each query you suspect and check the notes. If you are ready to parse a lot of queries, you can also do it automatically.

\n", "protected": false } }