Interpret the Explain Plan command

Similar Questions

• DECODE is changing the explain plan

  I have a statement with a decoding function in the where clause like this:
  

  AND decode(:cropcode,-1,'-1',sdu.u_crop_group) = decode(:cropcode,-1,'-1',:cropcode)

  When I have a package-1 as parameter for cropgroup the filter would result by ' AND '-1' = '-1', and the statement is executed in less than 2 seconds.»»» When I leave this where clause it takes almost 18 seconds. The result is the same so I don't understand why the explain plan command is so different and why not use index scans in the statement without decoding.
  
  Below plans to explain and tkprofs to 1 (no decode) and 2 (decode).
  
  * explain 1 *.
  {code}
  SQL statement that produced these data:
  Select * from table (dbms_xplan.display)
  
  PLAN_TABLE_OUTPUT
  
  ---------------------------------------------------------------------------------------------------------------
  | ID | Operation | Name | Lines | Bytes | TempSpc | Cost (% CPU).
  ---------------------------------------------------------------------------------------------------------------
  | 0 | SELECT STATEMENT | 7080 | 2413K | 43611 (2) |
  | 1. SORT ORDER BY | 7080 | 2413K | 5224K | 43611 (2) |
  |* 2 | FILTER |
  |* 3 | HASH JOIN | 7156. 2 438 K | 43075 (2) |
  | 4. TABLE ACCESS FULL | DWH_ABS_DETERMINATION | 17745. 363KO | 83 (0) |
  |* 5 | OUTER HASH JOIN | 7156. 2292K | 42991 (2) |
  |* 6 | HASH JOIN | 7156. 1355K | 42907 (2) |
  |* 7 | HASH JOIN | 6987. 1187K | 19170 (2) |
  |* 8 | HASH JOIN | 6947 | 963K | 10376 (1) |
  |* 9 | TABLE ACCESS BY INDEX ROWID | ALIQUOT | 3. 144. 3 (0) |
  | 10. NESTED LOOPS | 6907. 897K | 8577 (1) |
  | * 11 | HASH JOIN | 2264 | 187K | 1782 (2) |
  | 12. TABLE ACCESS BY INDEX ROWID | SAMPLE | 190. 4370. 17 (0) |
  | 13. NESTED LOOPS | 2264 | 152K | 107 (1) |
  | 14. NESTED LOOPS | 12. 552. 25 (0) |
  | * 15 | TABLE ACCESS FULL | SDG_USER | 12. 288. 13 (0) |
  | 16. TABLE ACCESS BY INDEX ROWID | SDG | 1. 22. 1 (0) |
  | * 17. INDEX UNIQUE SCAN | PK_SDG | 1 | | | 0 (0) |
  | * 18. INDEX RANGE SCAN | FK_SAMPLE_SDG | 597. 2 (0) |
  | 19. TABLE ACCESS FULL | SAMPLE_USER | 1078K | 16 M | 1669 (1) |
  | * 20. INDEX RANGE SCAN | FK_ALIQUOT_SAMPLE | 3 | | | 2 (0) |
  | 21. TABLE ACCESS FULL | ALIQUOT_USER | 3403K | 29 M | 1781 (3) |
  | 22. TABLE ACCESS FULL | TEST | 3423K | 104 M | 8775 (2) |
  | * 23. TABLE ACCESS FULL | RESULT | 3435K | 65 M | 23718 (2) |
  | 24. VIEW | PLATE | 21787 | 2851K | 84 (2).
  | * 25. FILTER |
  | 26. TABLE ACCESS FULL | PLATE | 21787 | 574K | 84 (2).
  | * 27. INDEX UNIQUE SCAN | PK_OPERATOR_GROUP | 1. 7 | | 0 (0) |
  | * 28. INDEX UNIQUE SCAN | PK_OPERATOR_GROUP | 1. 7 | | 0 (0) |
  | * 29. INDEX UNIQUE SCAN | PK_OPERATOR_GROUP | 1. 7 | | 0 (0) |
  | * 30 | INDEX UNIQUE SCAN | PK_OPERATOR_GROUP | 1. 7 | | 0 (0) |
  | * 31. INDEX UNIQUE SCAN | PK_OPERATOR_GROUP | 1. 7 | | 0 (0) |
  ---------------------------------------------------------------------------------------------------------------
  
  Information of predicates (identified by the operation identity card):
  ---------------------------------------------------
  
  2. ((«GROUP_ID» EST NULL ou EXISTE (SELECT / * + * / 0 DE "AGIL".) filter)) "OPERATOR_GROUP"
  "OPERATOR_GROUP' WHERE ' OPERATOR_ID"="LIMS$ OPERATOR_ID" () AND "GROUP_ID" =:B1)) AND ('GROUP_ID' IS NULL) "'". "
  OR EXISTS (SELECT / * + * / 0 "LIMS".) ' ' OPERATOR_GROUP ' 'OPERATOR_GROUP' WHERE
  "OPERATOR_ID"="LIMS$ OPERATOR_ID" () AND "GROUP_ID" =:B2)) AND ('GROUP_ID' IS NULL OR EXISTS (SELECT / * +)) "" "."
  * / 0 "LIMS". "' OPERATOR_GROUP ' 'OPERATOR_GROUP' WHERE ' OPERATOR_ID"="LIMS$ OPERATOR_ID" () AND "."
  (('GROUP_ID' =: B3)) AND ('GROUP_ID' IS NULL OR EXISTS (SELECT / * + * / 0 "LIMS".)) "" OPERATOR_GROUP ".
  'OPERATOR_GROUP' WHERE ' OPERATOR_ID "=" LIMS$ OPERATOR_ID "() AND"GROUP_ID "=:B4)))".
  3 - access ("U_ABS_DETERMINATION" ="DETERMINATION_ASSIGNMENT")
  5 - access("PLT".") PLATE_ID"(+) ="PLATE_ID")
  6 - access ("TEST_ID" ="TEST_ID")
  7 - access ("ALIQUOT_ID" ="ALIQUOT_ID")
  8 - access ("ALIQUOT_ID" ="ALIQUOT_ID")
  9 - filter("STATUS"='C' OR "STATUS"='P' OR "STATUS"='V')
  11 - access ("SAMPLE_ID" ="SAMPLE_ID")
  15 - filter ("U_ABS_DETERMINATION" IS NOT NULL AND "U_CLIENT_TYPE" = 'QC' AND
  "U_WEEK_OF_PROCESSING"= TO_NUMBER(:WEEK) AND "U_YEAR_OF_SAMPLE_DELIVERY' = TO_NUMBER (:YEAR)).
  17 - access ("SDG_ID" ="SDG_ID")
  18 - access ("SDG_ID" ="SDG_ID")
  20 - access ("SAMPLE_ID" ="SAMPLE_ID")
  23 - filter ('NAME' = 'End result')
  25 - filter("GROUP_ID" IS NULL OR EXISTS (SELECT /*+ */ 0 FROM "LIMS".")) OPERATOR_GROUP ".
  'OPERATOR_GROUP' WHERE ' OPERATOR_ID "=" LIMS$ OPERATOR_ID "() AND"GROUP_ID "=:B1))".
  27 - access ("GROUP_ID" =: B1 AND "OPERATOR_ID"="LIMS$ OPERATOR_ID" ())
  28 - access ("GROUP_ID" =: B1 AND "OPERATOR_ID"="LIMS$ OPERATOR_ID" ())
  29 - access ("GROUP_ID" =: B1 AND "OPERATOR_ID"="LIMS$ OPERATOR_ID" ())
  30 - access ("GROUP_ID" =: B1 AND "OPERATOR_ID"="LIMS$ OPERATOR_ID" ())
  31 - access ("GROUP_ID" =: B1 AND "OPERATOR_ID"="LIMS$ OPERATOR_ID" ())
  
  Note
  -----
  -"PLAN_TABLE' is old version
  {code}
  
  
  * tkprof 1 *.
  {code}
  
  TKPROF: Release 10.2.0.3.0 - Production on Tue Jan 13 13:21:47 2009
  
  Copyright (c) 1982, 2005, Oracle. All rights reserved.
  
  Trace file: C:\oracle\product\10.2.0\admin\nautp02\udump\nautp02_ora_880.trc
  Sorting options: by default
  
  ********************************************************************************
  Count = number of times OIC procedure has been executed
  CPU = time in seconds cpu execution
  elapsed = elapsed time in seconds the execution
  disc = number of physical reads from disk buffers
  Query = number of buffers for a consistent reading
  current = number of buffers in current mode (usually for the update)
  rows = number of rows processed by extracting or execute the call
  ********************************************************************************
  
  SELECT sdu.u_crop_group,
  SD. Name as sdg_name,
  ad.variety_name,
  ad.batch_number,
  B.SID as aliquot_name,
  Sau.u_box_code as box_code,
  Sau.u_box_position as box_position,
  t.Nom as test_name,
  r.original_result,
  PLT. Name as plate_name,
  Concat (chr (a.plate_row + 64), a.plate_column) as plate_position,
  au.u_replicate_number as replicate_number
  OF lims_sys.sdg sd,.
  lims_sys.sdg_user STO,
  lims_sys. Sample his.
  lims_sys.sample_user sau,
  lims_sys.aliquot has,
  to the lims_sys.aliquot_user,.
  lims_sys.test t,
  lims_sys. Result r,
  PLT lims_sys.plate,
  Ad lims_sys.abs_determination
  WHERE sd.sdg_id = sdu.sdg_id
  AND sd.sdg_id = sa.sdg_id
  AND sa.sample_id = sau.sample_id
  AND sau.sample_id = a.sample_id
  AND a.aliquot_id = au.aliquot_id
  AND au.aliquot_id = t.aliquot_id
  AND t.test_id = r.test_id
  AND plt.plate_id (+) = a.plate_id
  AND sdu.u_abs_determination = ad.determination_assignment
  AND a.status IN ('V', 'P', 'C')
  AND r.name = 'result '.
  AND sdu.u_client_type = "QC".
  AND sdu.u_year_of_sample_delivery = (: year)
  AND sdu.u_week_of_processing = (: week)
  - AND decode(:cropcode,-1,'-1',sdu.u_crop_group) = decode(:cropcode,-1,'-1',:cropcode)
  ORDER BY box_code, box_position, replicate_number
  
  call the query of disc elapsed to cpu count current lines
  ------- ------ -------- ---------- ---------- ---------- ---------- ----------
  Parse 1 0.00 0.00 0 0 0 0
  Run 1 1.15 1.16 0 0 0 0
  Fetch 1 8.53 16.10 227649 241266 0 500
  ------- ------ -------- ---------- ---------- ---------- ---------- ----------
  Total 3 9.68 17,27 227649 241266 0 500
  
  Chess in the library during parsing cache: 1
  Lack in the library during execution cache: 1
  Optimizer mode: ALL_ROWS
  The analysis of the user id: 97
  
  Rows Row Source operation
  ------- ---------------------------------------------------
  SORT ORDER BY 500 (cr = 241266 pr = 227649 pw = time 0 = 16104631 en)
  FILTER 21311 (cr = 241266 pr = 227649 pw = time 0 = 16246749 en)
  21311 HASH JOIN (cr = 241266 pr = 227649 pw = time 0 = 16225434 en)
  17745 TABLE ACCESS FULL DWH_ABS_DETERMINATION (cr = 374 pr = 0 pw = time 0 = 69 fr)
  21311 HASH JOIN RIGHT OUTER (cr = 240892 pr = 227649 pw = time 0 = 16170607 en)
  21895 VIEW PLATE (cr = 316 pr = 0 pw = time 0 = 43825 US)
  21895 FILTER (cr = 316 pr = 0 pw = time 0 = 43823 US)
  21895 TRAY FULL ACCESS (cr = 316 pr = 0 pw = time 0 = 31 US)
  0 INDEX UNIQUE SCAN PK_OPERATOR_GROUP (cr = 0 pr = 0 pw = time 0 = 0 US)(object id 45769)
  21311 HASH JOIN (cr = 240576 pr = 227649 pw = time 0 = 16106174 en)
  21311 HASH JOIN (cr = 133559 pr 121596 pw = time = 0 = 9594130 en)
  21311 HASH JOIN (cr = 94323 pr = 83281 pw = time 0 = 6917067 en)
  21311 HASH JOIN (cr = 86383 pr 75547 pw = time = 0 = 5509672 en)
  JOIN by HASH 7776 (cr = 8134 pr = 0 pw = time 0 = 285364 en)
  TABLE ACCESS BY INDEX ROWID SAMPLE 7776 (cr = 572 pr = 0 pw = time 0 = 27152 US)
  7876 NESTED LOOPS (cr = 377 pr = 0 pw = time 0 = 488287 en)
  JOIN by HASH 99 (cr = 160 pr = 0 pw = time 0 = US 4168)
  99 TABLE ACCESS FULL SDG_USER (cr = 53 pr = 0 pw = time 0 = US 1209)
  5719 TABLE ACCESS FULL SDG (cr = 107 pr = 0 pw = time 0 = 17 US)
  7776 INDEX RANGE SCAN FK_SAMPLE_SDG (cr = 217 pr = 0 pw = time 0 = 623 en)(object id 45990)
  1079741 TABLE ACCESS FULL SAMPLE_USER (cr = 7562 pr = 0 pw = time 0 = 24 US)
  3307948 TABLE ALIQUOT FULL ACCESS (cr = 78249 pr = pw 75547 time = 0 = 3331129 en)
  3406836 TABLE ACCESS FULL ALIQUOT_USER (cr = 7940 pr 7734 pw = time = 0 = 556 en)
  3406832 TABLE TEST FULL ACCESS (cr = 39236 pr 38315 pw = time = 0 = 3413192 en)
  3406832 TABLE ACCESS FULL RESULTS (cr = 107017 pr = 106053 pw = time 0 = 6848487 en)
  0 INDEX UNIQUE SCAN PK_OPERATOR_GROUP (cr = 0 pr = 0 pw = time 0 = 0 US)(object id 45769)
  0 INDEX UNIQUE SCAN PK_OPERATOR_GROUP (cr = 0 pr = 0 pw = time 0 = 0 US)(object id 45769)
  0 INDEX UNIQUE SCAN PK_OPERATOR_GROUP (cr = 0 pr = 0 pw = time 0 = 0 US)(object id 45769)
  0 INDEX UNIQUE SCAN PK_OPERATOR_GROUP (cr = 0 pr = 0 pw = time 0 = 0 US)(object id 45769)
  
  ********************************************************************************
  
  Select 'x '.
  Of
  Double
  
  
  call the query of disc elapsed to cpu count current lines
  ------- ------ -------- ---------- ---------- ---------- ---------- ----------
  Parse 1 0.00 0.00 0 0 0 0
  Run 1 0.00 0.00 0 0 0 0
  Fetch 1 0.00 0.00 0 0 0 1
  ------- ------ -------- ---------- ---------- ---------- ---------- ----------
  Total 3 0.00 0.00 0 0 0 1
  
  Chess in the library during parsing cache: 0
  Optimizer mode: ALL_ROWS
  The analysis of the user id: 97
  
  Rows Row Source operation
  ------- ---------------------------------------------------
  1 DOUBLE QUICK (cr = 0 pr = 0 pw = time 0 = 3 US)
  
  ********************************************************************************
  
  Start: id: = sys.dbms_transaction.local_transaction_id; end;
  
  
  call the query of disc elapsed to cpu count current lines
  ------- ------ -------- ---------- ---------- ---------- ---------- ----------
  Parse 1 0.00 0.00 0 0 0 0
  Run 1 0.00 0.00 0 0 0 1
  Fetch 0 0.00 0.00 0 0 0 0
  ------- ------ -------- ---------- ---------- ---------- ---------- ----------
  Total 2 0.00 0.00 0 0 0 1
  
  Chess in the library during parsing cache: 0
  Optimizer mode: ALL_ROWS
  The analysis of the user id: 97
  
  
  
  ********************************************************************************
  
  TOTALS FOR ALL NON RECURSIVE INSTRUCTIONS
  
  call the query of disc elapsed to cpu count current lines
  ------- ------ -------- ---------- ---------- ---------- ---------- ----------
  Parse 3 0.00 0.00 0 0 0 0
  Run 3 1.15 1.16 0 0 0 1
  Pick 2 8.53 16.10 227649 241266 0 501
  ------- ------ -------- ---------- ---------- ---------- ---------- ----------
  Total 8 9.68 17,27 227649 241266 0 502
  
  Chess in the library during parsing cache: 1
  Lack in the library during execution cache: 1
  
  
  TOTALS FOR ALL RECURSIVE INSTRUCTIONS
  
  call the query of disc elapsed to cpu count current lines
  ------- ------ -------- ---------- ---------- ---------- ---------- ----------
  Parse 30 0.00 0.00 0 0 0 0
  Run 30 0.00 0.00 0 0 0 0
  Get 30 0.00 0.00 0 40 0 10
  ------- ------ -------- ---------- ---------- ---------- ---------- ----------
  Total 90 0.00 0.00 0 40 0 10
  
  Chess in the library during parsing cache: 0
  
  3 the session user SQL statements.
  30 internal to SQL statements in session.
  33 SQL statements in session.
  ********************************************************************************
  Trace file: C:\oracle\product\10.2.0\admin\nautp02\udump\nautp02_ora_880.trc
  Compatibility of trace files: 10.01.00
  Sorting options: by default
  
  8 sessions in the trace file.
  3 SQL statements of the user in the trace file.
  30 internal SQL instructions in the trace file.
  33 SQL statements in the trace file.
  6 unique SQL statements in the trace file.
  633 lines in the trace file.
  23 seconds in the trace file.
  {code}

  ZI wrote:
  I have a statement with a decoding function in the where clause like this:

  AND decode(:cropcode,-1,'-1',sdu.u_crop_group) = decode(:cropcode,-1,'-1',:cropcode)
  

  When I have a package-1 as parameter for cropgroup the filter would result by ' AND '-1' = '-1', and the statement is executed in less than 2 seconds.»»» When I leave this where clause it takes almost 18 seconds. The result is the same so I don't understand why the explain plan command is so different and why not use index scans in the statement without decoding.

  I would interpret the results displayed differently.

  Execution which took 17 s according to the 241 266 coherent block played tkprof output gets but in order to do so he read 227 649 the disk blocks. Note that most of the table addressed by this query blocks were read through scanning of complete table that can take advantage of multiple blocks readings, for example if you unset the db_file_multiblock_read_count 10.2 (recommended) it usually try to read 1 MB with a read request, which are 128 blocks in case of standard block size 8 k. Due to several reasons not always the full size can be requested with each read request, lets say about 200 000 blocks could have been read by about 2,000 blocks multiple readings. Each read request would turn into a physical read, could you get an estimate approximate 25 MS per read times 2,000 applications-online 50 seconds (your system is running obviously better that the average assumed by ost g 10 base optimizer without collected statistics system workload, can be that some additional file caching system is involved).

  On the other hand, the execution plan that finished within 2 seconds completed 221 420 coherent block gets but did No physical reads at all. Note that most of the table blocks should be processed using one-piece random searches (ACCESS BY ROWID of the TABLE), according to the grouping of the indices factor, it could have been as many blocks that the lines have been returned to the range index scans. So you could have done with lets say more than 60,000 randomly accessed table blocks => until 60 000 monobloc required reading. So in the worst case, this may take 60 000 requests time 10ms by read-online 600 seconds, even if in reality at least some of the blocks will be stored in the buffer cache, so it should be less.

  It would be interesting to know how these two declarations with a cold buffer cache, so that both had to physical reads. I suppose the first is actually faster. Of course, if the second corresponds more to your typical situation that most of the blocks is in the buffer anyway, then it could be faster, because the blocks read by random access are more likely to stay in memory blocks read by complete sweep of the table, but in a true perspective of I/O the first is expected to be higher.

  Moreover, the change in the plan is probably caused by the fact that the additional predicate (DECODING) lowers the cardinality of the table of SDG_USER conduct so that LOOP IMBRIQUEE approach seems to be cheaper to the optimizer that the hash join/full scan table approach. Apparently the estimate is way off (by two orders of magnitude, in fact 100 instead of 1), then the plan is not really cheap, because it seems like the optimizer.

  By the way: two actual execution plans displayed in the output from tkprof are actually different from the displayed output of EXPLAIN the PLAN, so the statement has executed a little differently provided the facility to EXPLAIN the PLAN.

  Your PLAN_TABLE is old, since you are on 10g you should drop any PLAN_TABLEs that are in non - SYS diagrams, since 10 g already provides a global temporary Table as part of the default dictionary (SYS. Plan_table$ presentations via public synonym PLAN_TABLE).

  Kind regards
  Randolf

  Oracle related blog stuff:
  http://Oracle-Randolf.blogspot.com/

  SQLTools ++ for Oracle (Open source Oracle GUI for Windows):
  http://www.sqltools-plusplus.org:7676 /.
  http://sourceforge.NET/projects/SQLT-pp/

• Explain the explain plan

  decide to move to optimization soon. Book says join faster that the subquery in this example because the analyses involved. The "cost" to the subquery appears lower than the cost for the join. So it is confusing to me - aka How should I be interpreting this.

  Plan of subquery:

  

  join plan

  

  as you can see that the plan for the subquery has less than a cost. Could someone explain these outputs as to which application is more effective. I need to start somewhere.

  Thank you!

  The BEST way to get help when you ask questions is:

  1 ask questions on SPECIFIC things

  2. tell us EXACTLY what term, value, etc. ask abaout

  Book says join faster that the subquery in this example because the analyses involved. The "cost" to the subquery appears lower than the cost for the join. So it is confusing to me - aka How should I be interpreting this.

  OK - what BOOK are you talking about? There is not much interest to mention a book if you're not going to tell us which book it and provide a link to it and even a page number. This gives us the SCOPE of your question.

  This "cost for the subquery" are you talking about? Be specifc. It is in one of the plans that you posted? What plan? Whose cost is it? For example, you could say:

  I have a question for the foreground below. Why is the cost to the xx line lower than the cost of the second plan on line AA?

  This question refers CLEARLY to the info we're talking. The way in which you stating the question, we try to guess what plan and the lines you want to say.

  subquery plan:
  
  
  join plan
  
  
  as you can see the subquery plan has less of a cost. Could someone explain from these outputs as to which query is more efficient. I need to start from somewhere.
  

  Are you talking about line #1 in each of these plans?

  Please edit your post and tell us EXACTLY what you ask in the topic and refer to values and SPECIFIC lines. Also post a link to the book and a reference to a page number you got the information from.

  The optimizer generally chooses the REAL implementation with the lowest cost plan. It is not clear whether the plans that you have posted are ACTUAL spending plans that Oracle really determined and used or just explain plans.for what Oracle thought it might use.

  If the statistics are not up-to-date these plans do not yet reflect the reality of the data.

  And if the amount of data is a small number of blocks or other of these plans can run better than the other in reality.

  You can find this Oracle white paper "Explain the Plan explaining" useful

  http://www.Oracle.com/technetwork/database/bi-Datawarehousing/TWP-explain-the-explain-plan-052011-393674.PDF

• To the topic to explain the query Plan

  Hello
  
  I have a question about the explain plan command. While gather us statistics and optimize, then choose the best possible plan out the plans explain command available. If we collect statistics on a table for a long time while the system choose:
  
  Whether it will continue to use the same plan, since it uses at startup when statistics have been collected, or will change the plan as soon as dml activities and statistics grow old.
  
  Thank you
  GK

  Gulshan says:
  Hello

  I have a question about the explain plan command. While gather us statistics and optimize, then choose the best possible plan out the plans explain command available. If we collect statistics on a table for a long time while the system choose:

  The same plan he chose to start with previous statistics. The plan will not change automatically as long as you update the statistics.

  Whether it will continue to use the same plan, since it uses at startup when statistics have been collected, or will change the plan as soon as dml activities and statistics grow old.

  The DML will not be able to change the statistics stored in the data dictionary views themselves. There must be a statistic explicit collection that has come to reflect the change in the data dictionary. 10 g from, there is automatically a task (a special 11 g automatic) is there who can detect the change in the ongoing dml on the table and can trigger the table for update statistics.

  Aman...

• explain plan for the same query diff

  Hi experts,

  Please, help me understand explain the plan.  I have tow Server (server and two server). The server are same table, even the type of database, even version Oracle (gr 11 (2), same operating system (linux Redhat 5.5) and same table and index.

  but when I explain the plan for the same query on the two server. I got diff--diff to explain the plan. reason it has different, according to my understanding, it should be same. explain please, I share the explain plan and lower indices for the two server.

  Server a

  SQL > col COLUMN_NAME format a20

  SQL > select index_name, column_name, position_colonne from user_ind_columns where table_name = 'LOAN_RUNNING_DETAILS_SOUTH"of order 1.

  INDEX_NAME COLUMN_NAME POSITION_COLONNE

  ------------------------------ -------------------- ---------------

  DATE_IND1_S LOANDATETIME 1

  IND_MSI_LN_LNS1_S MSISDN 1

  IND_MSI_LN_LNS1_S LOANDATETIME 2

  IND_MSI_LN_LNS1_S LOANSTATUS 3

  LAST_INDEX L_INDX_MSISDN_S 1

  MSISDN L_INDX_MSISDN_S 2

  SQL > select decode (status, 'N/a', 'Part Hdr', 'Global') ind_type, index_name, NULL nom_partition, status

  2 from user_indexes where table_name = 'LOAN_RUNNING_DETAILS_SOUTH '.

  3 union

  4. Select 'Local' ind_type, index_name, nom_partition, status

  5 to user_ind_partitions where index-name in (select index_name in user_indexes where table_name = 'LOAN_RUNNING_DETAILS_SOUTH')

  6 order of 1,2,3;

  IND_TYPE INDEX_NAME NOM_PARTITION STATUS

  -------- ------------------------------ ------------------------------ --------

  Global DATE_IND1_S VALID

  Global IND_MSI_LN_LNS1_S VALID

  Global L_INDX_MSISDN_S VALID

  SQL > explain plan for the small circle of MSISDN, TID, of LOAN_RUNNING_DETAILS_SOUTH where LOANDATETIME < = sysdate-2 and LOANDATETIME > sysdate-15 and LOANTYPE = 1;

  He explained.

  SQL > SQL > set line 200

  @?/rdbms/admin/utlxpls.sql

  SQL >

  PLAN_TABLE_OUTPUT

  --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

  Hash value of plan: 3659874059

  ------------------------------------------------------------------------------------------------------------------

  | ID | Operation | Name                       | Lines | Bytes | Cost (% CPU). Time | Pstart. Pstop |

  ------------------------------------------------------------------------------------------------------------------

  |   0 | SELECT STATEMENT |                            |  1448K |    58 M | 21973 (2) | 00:04:24 |       |       |

  |*  1 |  FILTER |                            |       |       |            |          |       |       |

  |   2.   PARTITION LIST ALL |                            |  1448K |    58 M | 21973 (2) | 00:04:24 |     1.    11.

  |*  3 |    TABLE ACCESS FULL | LOAN_RUNNING_DETAILS_SOUTH |  1448K |    58 M | 21973 (2) | 00:04:24 |     1.    11.

  ------------------------------------------------------------------------------------------------------------------

  PLAN_TABLE_OUTPUT

  --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

  Information of predicates (identified by the operation identity card):

  ---------------------------------------------------

  1 - filter(SYSDATE@!-2>SYSDATE@!-15)

  3 - filter("LOANTYPE"=1 AND "LOANDATETIME">SYSDATE@!-15 AND "LOANDATETIME"<=SYSDATE@!-2)

  16 selected lines.

  Second server

  SQL > select index_name, column_name, position_colonne from user_ind_columns where table_name = 'LOAN_RUNNING_DETAILS_SOUTH"of order 1.

  INDEX_NAME COLUMN_NAME POSITION_COLONNE

  ------------------------------ -------------------- ---------------

  DATE_IND1_S LOANDATETIME 1

  IND_MSI_LN_LNS1_S MSISDN 1

  IND_MSI_LN_LNS1_S LOANDATETIME 2

  IND_MSI_LN_LNS1_S LOANSTATUS 3

  LAST_INDEX L_INDX_MSISDN_S 1

  MSISDN L_INDX_MSISDN_S 2

  SQL > select decode (status, 'N/a', 'Part Hdr', 'Global') ind_type, index_name, NULL nom_partition, status

  2 from user_indexes where table_name = 'LOAN_RUNNING_DETAILS_SOUTH '.

  Union

  3 4 Select 'Local' ind_type, index_name, nom_partition, status

  5 to user_ind_partitions where index-name in (select index_name in user_indexes where table_name = 'LOAN_RUNNING_DETAILS_SOUTH')

  6 order of 1,2,3;

  IND_TYPE INDEX_NAME NOM_PARTITION STATUS

  -------- ------------------------------ ------------------------------ --------

  Global DATE_IND1_S VALID

  Global IND_MSI_LN_LNS1_S VALID

  Global L_INDX_MSISDN_S VALID

  SQL > explain plan for the small circle of MSISDN, TID, of LOAN_RUNNING_DETAILS_SOUTH where LOANDATETIME < = sysdate-2 and LOANDATETIME > sysdate-15 and LOANTYPE = 1;

  SQL > set line 200

  @?/rdbms/admin/utlxpls.sql

  SQL >

  PLAN_TABLE_OUTPUT

  --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

  Hash value of plan: 1161680601

  ----------------------------------------------------------------------------------------------------------------------------------

  | ID | Operation | Name                       | Lines | Bytes | Cost (% CPU). Time | Pstart. Pstop |

  ----------------------------------------------------------------------------------------------------------------------------------

  |   0 | SELECT STATEMENT |                            |     2.    84.     5 (0) | 00:00:01 |       |       |

  |*  1 |  FILTER                             |                            |       |       |            |          |       |       |

  |*  2 |   TABLE ACCESS BY INDEX ROWID | LOAN_RUNNING_DETAILS_SOUTH |     2.    84.     5 (0) | 00:00:01 | ROWID | ROWID |

  |*  3 |    INDEX RANGE SCAN | DATE_IND1_S |     2.       |     3 (0) | 00:00:01 |       |       |

  ----------------------------------------------------------------------------------------------------------------------------------

  PLAN_TABLE_OUTPUT

  --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

  Information of predicates (identified by the operation identity card):

  ---------------------------------------------------

  1 - filter(SYSDATE@!-2>SYSDATE@!-15)

  2 - filter ("LOANTYPE" = 1)

  3 - access("LOANDATETIME">SYSDATE@!-15 AND "LOANDATETIME"<=SYSDATE@!-2)

  17 selected lines.

  Reg,

  Hard

  Hi , HemantKChitale,

  I also update statistics manual as you say, but not see 'TABLE ACCESS FULL' good result

  What should I do? my need of production tuning, but I cannot able tune this...

  SQL > exec dbms_stats.gather_table_stats (-online 'ttt' ownname, tabname => 'LOAN_RUNNING_DETAILS_SOUTH', cascade => TRUE, estimate_percent => NULL, method_opt => 'for all columns size 254', => of degree 4);

  PL/SQL procedure successfully completed.

  SQL > explain plan for the small circle of MSISDN, TID, of LOAN_RUNNING_DETAILS_SOUTH where LOANDATETIME<=sysdate-2 and="" loandatetime="">sysdate-15 and LOANTYPE = 1;

  He explained.

  SQL > set line 200

  @?/rdbms/admin/utlxpls.sql

  SQL >

  PLAN_TABLE_OUTPUT

  --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

  Hash value of plan: 3659874059

  ------------------------------------------------------------------------------------------------------------------

  | ID | Operation | Name                       | Lines | Bytes | Cost (% CPU). Time | Pstart. Pstop |

  ------------------------------------------------------------------------------------------------------------------

  |   0 | SELECT STATEMENT |                            |  1874K |    75 M | 19626 (2) | 00:03:56 |       |       |

  |*  1 |  FILTER |                            |       |       |            |          |       |       |

  |   2.   PARTITION LIST ALL |                            |  1874K |    75 M | 19626 (2) | 00:03:56 |     1.    11.

  |*  3 |    TABLE ACCESS FULL | LOAN_RUNNING_DETAILS_SOUTH |  1874K |    75 M | 19626 (2) | 00:03:56 |     1.    11.

  ------------------------------------------------------------------------------------------------------------------

  PLAN_TABLE_OUTPUT

  --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

  Information of predicates (identified by the operation identity card):

  ---------------------------------------------------

  1 - filter(SYSDATE@!-2>SYSDATE@!-15)

  3 - filter("LOANDATETIME">SYSDATE@!-15 AND "LOANTYPE"=1 AND "LOANDATETIME")<>

  16 selected lines.

• I have the following plan to explain, but I don't know how interperent it

  Hello all;
  
  I have the explain plan following below obtained pl/sql developer, but I don't know how to interperent or use it for my performance problem
  

  PLAN_TABLE_OUTPUT          
             
  ----------------------------------------------------------------------------------------          
  | Id  | Operation                       |  Name                | Rows  | Bytes | Cost  |          
  ----------------------------------------------------------------------------------------          
  |   0 | SELECT STATEMENT                |                      |     1 |   108 |   932 |          
  |   1 |  SORT GROUP BY                  |                      |     1 |   108 |   932 |          
  |*  2 |   TABLE ACCESS BY INDEX ROWID   | OPERATION            |     1 |    34 |    12 |          
  |   3 |    NESTED LOOPS                 |                      |     1 |   108 |   929 |          
  |   4 |     NESTED LOOPS                |                      |     1 |    74 |   917 |          
  |*  5 |      HASH JOIN                  |                      |     1 |    60 |   916 |          
  |*  6 |       TABLE ACCESS FULL         | WORK_ORDER           |  1302 | 46872 |   787 |          
  |*  7 |       TABLE ACCESS FULL         | SERIALIZATION_TRACE  |   129K|  3044K|   123 |          
  |*  8 |      TABLE ACCESS BY INDEX ROWID| PART                 |     1 |    14 |     1 |          
  |*  9 |       INDEX UNIQUE SCAN         | SYS_C004302          |     1 |       |       |          
  |* 10 |     INDEX RANGE SCAN            | RCLX_OPERATION_3     |     1 |       |    11 |          
  ----------------------------------------------------------------------------------------          
             
  Predicate Information (identified by operation id):          
  ---------------------------------------------------          
             
     2 - filter("O"."RESOURCE_ID" LIKE 'TEST%')          
     5 - access("W"."BASE_ID"="PT"."WORKORDER_BASE_ID" AND           
                "W"."LOT_ID"="PT"."WORKORDER_LOT_ID" AND "W"."SPLIT_ID"="PT"."WORKORDER_SPLIT_ID" AND 
                "W"."SUB_ID"="PT"."WORKORDER_SUB_ID")          
     6 - filter("W"."TYPE"='W' AND "W"."PART_ID" IS NOT NULL AND "W"."PART_ID"<>'RMA' AND           
                "W"."PART_ID"<>'REWORK' AND "W"."CLOSE_DATE">=TO_DATE('2010-01-01 00:00:00',           
                'yyyy-mm-dd hh24:mi:ss') AND "W"."CLOSE_DATE"<=TO_DATE('2010-12-31 00:00:00',           
                'yyyy-mm-dd hh24:mi:ss'))          
     7 - filter("PT"."SERIAL_NUMBER"<>'N/A')          
     8 - filter("P"."PLANNER_USER_ID"='CCA')          
     9 - access("W"."PART_ID"="P"."ID")          
         filter("P"."ID"<>'RMA' AND "P"."ID"<>'REWORK')          
    10 - access("W"."SUB_ID"="O"."WORKORDER_SUB_ID" AND           
                "W"."BASE_ID"="O"."WORKORDER_BASE_ID" AND "W"."LOT_ID"="O"."WORKORDER_LOT_ID" AND 
                "W"."SPLIT_ID"="O"."WORKORDER_SPLIT_ID")          
         filter("W"."BASE_ID"="O"."WORKORDER_BASE_ID" AND           
                "W"."LOT_ID"="O"."WORKORDER_LOT_ID" AND "W"."SPLIT_ID"="O"."WORKORDER_SPLIT_ID")     
             
  Note: cpu costing is off          
            

  Here are a few slides that I use when I present to you how to read explain plans:
  http://www.morganslibrary.org/Pres/lad/cloug_1_xplan.PDF

  |*  6 |        TABLE ACCESS FULL         | WORK_ORDER           |  1302 | 46872 |   787 |
  |*  7 |       TABLE ACCESS FULL         | SERIALIZATION_TRACE  |   129K|  3044K|   123 |
  

  Essentially, your question is here. you read a lot of lines to return alone. Do you need them all? To get them you do full table scan on the two tables? An index would help?

  and yes I am voluntarily is not giving you the answers but rather to point you in the right direction to find it yourself.

  On the one hand, I don't know your version, your SQL, or what indexes exist.

• 4.0 EA1 - new explain Plan feature

  Hi I was trying simply the new explain Plan feature (I like the look of) mentioned by Jeff Smith on his blog but if I get an "ORA-00942: table or view does not exist.

  I get it doing the explain plan drop-down command selecting from V$ SQL_PLAN (synonym) and underlying base table V_$ SQL_PLAN. I am logged in as APPS, but that the user has select privileges on these objects sys to me. Don't know how you / he's got it to work (logged in as sys?) or if I give missing?

  Paul

  Grant select any dictionary apps privilege. Or, if your DBA prefers giving finer privileges on individual objects, you must also select on V$ SQL and V$ SQL_PLAN_STATISTICS.

• Developer SQL explain plan

  I ran some queries and their plan to explain in the sql developer. I not issue an insert or update all statement. No change to the database, but when I tried to unplug it wonder there are a few changes and ask me if I want to commit or rollback etc.
  
  Why so much? I'm afraid to choose an any of them because I don't know who has change his talk.
  
  It has happened several times and feel that it has something to with market explain plan in SQL developer.
  
  
  Everyone comments on it? I'd appreciate that.
  
  TX,

  I guess that changes made to the plan table (where your explain plan command goes).

  TUBBY_TUBBZ?select PLAN_ID from plan_table;
  
  no rows selected
  
  Elapsed: 00:00:00.01
  TUBBY_TUBBZ?explain plan for select PLAN_ID from plan_table;
  
  Explained.
  
  Elapsed: 00:00:00.00
  TUBBY_TUBBZ?select PLAN_ID from plan_table;
  
             PLAN_ID
  ------------------
                  33
                  33
  
  2 rows selected.
  
  Elapsed: 00:00:00.01
  TUBBY_TUBBZ?
  

  Which, if you trace through the synonym you will find that it is a global temporary table owned by SYS.

  GLOBAL TEMPORARY TABLE "SYS"."PLAN_TABLE$"
  

  So you can save your changes or not, it won't matter because the data will disappear when your session disconnects.

• Explain plan aid starts to column

  SELECT *
  FROM emp
  WHERE NOT EXISTS (SELECT 0
                    FROM dept
                    WHERE dept.dname = 'SALES' AND dept.deptno = emp.deptno)
  AND NOT EXISTS (SELECT 0
                  FROM bonus
                  WHERE bonus.ename = emp.ename)
  
  ------------------------------------------------------------------
  | Id  | Operation                    | Name    | Starts | A-Rows |
  ------------------------------------------------------------------
  |   0 | SELECT STATEMENT             |         |      1 |      8 |
  |*  1 |  FILTER                      |         |      1 |      8 |
  |   2 |   TABLE ACCESS FULL          | EMP     |      1 |     14 |
  |*  3 |   TABLE ACCESS BY INDEX ROWID| DEPT    |      3 |      1 |
  |*  4 |    INDEX UNIQUE SCAN         | DEPT_PK |      3 |      3 |
  |*  5 |   TABLE ACCESS FULL          | BONUS   |      8 |      0 |
  ------------------------------------------------------------------
  

  In the above execution plan. For ID 5, means he did 8 on table BONUS full table scan?

  Is the order of execution 2,4,3,5,1,0?

  > I have to disagree with you on the 'order' (and agree with the OP). The term is subject to interpretation...

  Ok.

  My definition is that the FILTER operation is "pulled" for each product line by FULL of EMP table scan.

  I think I'll avoid the question "in what order do the beginning of operations" tend toward "how to interpret the execution plan" and "how data flow?

• Need to explain Plan output in HTML format

  Hello

  I have details slider sqlid and child. And I'm able to generate explain plan SQL running as below

  SELECT * FROM table (DBMS_XPLAN. DISPLAY_CURSOR('xxxxxxxxxxxxxx',0,'ALLSTATS'));

  I need send the output of this customer. and the problem is the customer wants in HTML format. Advice to reel in HTML format

  concerning

  Pravin

  You can always query the PLAN_TABLE directly, and use SQL * more to empty in HTML.

  Another option is to do this with SQL Developer. Paste the SQL statement into the worksheet, and then press the explain Plan. When you see the plan, right-click on it and choose export as HTML.

  See you soon,.
  Brian

• Need help with understanding explain plan

  Hi all

  I'm trying to understand the subject of the explain Plan, and while I was reading a document and from there I found one of the query that is below:

  Query

  SELECT A.customer_name,

  Count (distinct b.invoice_id) 'open invoices. "

  Count (c.invoice_id) "open invoice".

  Clients has,

  b invoices,

  c invoices_items

  WHERE b.invoice_status = 'OPEN'

  AND A.customer_id = b.customer_id

  AND c.invoice_id (+) = b.invoice_id

  A.customer_name GROUP

  Explain Plan

  See attached file...

  

  I appreciate if someone explain this attached plan really explain in detail for my purpose of learning. Thanks in advance

  Concerning

  Muzz

  I'm trying to understand the subject of the explain Plan

  Excellent!

  I suggest you just started reading the book of Maria Colgan white "Explain the explain Plan".

  http://www.Oracle.com/technetwork/database/bi-Datawarehousing/TWP-explain-the-explain-plan-052011-393674.PDF

  This white paper examines the different lines, you will see in a plan and what they mean.

• Look at an explain plan

  version 11.2.0.4.0

  Solaris x 64 operating system

  Toad 9.0

  Hi, I'm trying to give a new user privleges see explain the plan. for this, I did the following

  grant select_catalog_role < username >;

  Grant execute on sys.dbms_xplan_type < username >;

  Grant execute on sys.dbms_xplan_type_table < username >;

  It didn't work, and then I have granted the select privilege on the table of existing plan to a new user.

  Grant select on sys.plan_table < username >;

  create synonym plan_table for sys.plan_table

  Yet it did not work, I got the error "ORA-01031: insufficient privileges" when you try to view explain plan.

  I even tried to create a new table of plan in this new scheme of the user by running the utlxplan.sql, but I get an error message saying that the table already exists.

  can someone help me please on where I'm wrong.

  Thank you

  «The question one EXPLAIN PLAN statement, you must have the necessary privileges to insert rows into a table of existing output that you specify to hold execution plan.»

  You must also have the necessary privileges to run the SQL statement to determine the execution plan. If the SQL statement accesses a view, you must have privileges to access any tables and views on which the opinion is based. If the view is of another opinion which is based on a table, you must have privileges to access the other point of view and its underlying table.

  To examine the execution plan produced by a EXPLAIN PLAN statement, you must have the necessary privileges to query the table of output.

  The EXPLAIN PLAN statement is a statement data manipulation language (DML), rather than a data definition language (DDL) statement. Therefore, Oracle database does not implicitly commit changes made by one EXPLAIN PLAN statement. If you want to keep the lines that are generated by a EXPLAIN PLAN in the output table, then you must commit to the transaction that contains the statement. »

  http://docs.Oracle.com/CD/E16655_01/server.121/e17209/statements_9010.htm#sthref6316

• Explain plan used

  Hello

  on 11.2.0.3, I use the following to check the explain Plan used for an executed query.

  SELECT * FROM
  TABLE (DBMS_XPLAN. DISPLAY_AWR ('< sql_id >', '< plan_hash >'));

  For example

  SELECT * FROM TABLE (DBMS_XPLAN. DISPLAY_AWR ('cx8m90z5n57g1','3867296312'));

  The problem is that it does not always return a result to display. Every now and then it does not find any Plan to explain. Why?

  Any other way that find a used Plan explain for sure?

  Thank you and best regards.

  SQL cannot be captured by AWR as he may not be among the SQLs ' n top of page in a snapshot.

  However, if the SQL code is still present in the cache of the library, you can use DBMS_XPLAN. DISPLAY_CURSOR

  Hemant K Collette

• Explain plan shows no relevant tables

  Hi all
  
  spin 10.2.0.4 on solaris
  
  
  I have a duration long query explain plan... The explain plan displays the name of the other tables (table full access) that don't exist anywhere in the query that problem...
  
  
  Please notify
  
  Kai

  "BOLD" names the table not in the query (* IVM_INVOICE_RECORD *)

  They are referenced in the ARM_SUBS_BALANCE view.

• Help to understand the plan of the explain command

  Hello world

  I have a question:

  INSERT INTO ICM_UPSEL_1_ALL

  Select a.customer_no, a.pr_code_bbl, pr_code_pmm, a.score, a.price_diff, a.flag (b.pr_code_pmm) min

  ICM_UPSEL_MIN_PRDIFF_1 a, icm_pre b

  where a.customer_no = b.customer_no

  and a.pr_code_bbl = b.pr_code_bbl

  and a.score = b.score

  and a.flag = b.flag

  and a.price_diff = b.price_diff

  and b.price_diff > 0

  and b.score > = 0.5

  and b.flag = 1

  and b.price_diff > 0 and b.price_diff < = 10

  Group of a.customer_no, a.pr_code_bbl, a.score, a.price_diff, a.flag

  This query runs in a pl/sql procedure.  The plan of the explain for this query command is:

  Hash value of plan: 3124235498

  ------------------------------------------------------------------------------------------------------------------

  | ID | Operation | Name                           | Lines | Bytes | Cost (% CPU). Time |

  ------------------------------------------------------------------------------------------------------------------

  |   0 | INSERT STATEMENT.                                |     1.   143.     4 (25) | 00:00:01 |

  |   1.  LOAD TABLE CLASSIC | ICM_UPSEL_1_ALL |       |       |            |          |

  |   2.   HASH GROUP BY.                                |     1.   143.     4 (25) | 00:00:01 |

  |   3.    NESTED LOOPS |                                |       |       |            |          |

  |   4.     NESTED LOOPS |                                |     1.   143.     3 (0) | 00:00:01 |

  |*  5 |      TABLE ACCESS BY INDEX ROWID | ICM_UPSEL_MIN_PRDIFF_1 |     1.    65.     1 (0) | 00:00:01 |

  |*  6 |       INDEX RANGE SCAN | MPD_1_FLAG_IDX |     1.       |     1 (0) | 00:00:01 |

  |*  7 |      INDEX RANGE SCAN | ICM_PRE_FLAG_IDX |     1.       |     2 (0) | 00:00:01 |

  |*  8 |     TABLE ACCESS BY INDEX ROWID | ICM_PRE |     1.    78.     2 (0) | 00:00:01 |

  ------------------------------------------------------------------------------------------------------------------

  Information of predicates (identified by the operation identity card):

  ---------------------------------------------------

  5 - filter("A".") PRICE_DIFF"> 0 AND 'A '. "SCORE" > = 0.5 AND 'A' "." " (PRICE_DIFF"< = 10)

  6 - access("A".") FLAG "= 1)

  7 - access("B".") FLAG "= 1)

  8 - filter("B".") PRICE_DIFF"< = 10 AND 'B '. "SCORE" > = 0.5 AND 'B' "." " PRICE_DIFF"> 0 AND

  "A"." CUSTOMER_NO '=' B '. "' CUSTOMER_NO ' AND 'A '. "" PR_CODE_BBL "=" B ". "' PR_CODE_BBL ' AND 'A '. "SCORE" = 'B' "." " SCORE '.

  AND 'A '. "" PRICE_DIFF "=" B ". ("' PRICE_DIFF")

  This query runs for 10 hours now and still no results.  Could someone please help me where goes wrong... Why is - it take as long to insert data...

  The number of rows in ICM_UPSEL_MIN_PRDIFF_1: 84 858

  The number of rows in icm_pre: 455,500,944

  All columns are indexed.

  My version of the database is 11.1.0.6 running on windows server 2003 R2.

  Thanks in advance

  This plan seems much more suitable for me: instead of doing > 80 K of the loops of the CBO now decides to make a unique HASH JOIN. I would try to run the operation with the dynamic_sampling flag. If the system statistics are not completely misleading the operation now only takes a few minutes (and no 10: 00 >).

  Concerning

  Martin