What is left of explain plan with ASSM?

From: Polarski, Bernard <Bernard.Polarski_at_atosorigin.com>
Date: Thu, 19 Oct 2006 13:52:03 +0200
Message-ID: <25D4919915CCF742A88EE3366D6D913D0FB9F9BF@mailserver1>

What is left with explain plan value nowadays when ASSM is in house? I got his from explain plan but the real executions show that there is no problems:
The problem seems that the optimiser sees fantastic clustering factor. Note the prediction of 568 table block access in contrast of the reality.

Execution Plan

0 SELECT STATEMENT Optimizer=CHOOSE (Cost=74 Card=648 Bytes=17496)

1 0 SORT (ORDER BY) (Cost=74 Card=648 Bytes=17496)

   2    1     HASH JOIN (Cost=71 Card=648 Bytes=17496)
   3    2       TABLE ACCESS (BY INDEX ROWID) OF 'ASSIGNMENTS' (Cost=56
Card=568 Bytes=9656)
   4    3         INDEX (RANGE SCAN) OF 'ASG_002' (NON-UNIQUE) (Cost=3
Card=568)
   5    2       TABLE ACCESS (FULL) OF 'TRAINING_EVENTS' (Cost=14 Card

=23587 Bytes=235870)

Statistics

         14  recursive calls
          0  db block gets
          7  consistent gets
          0  physical reads
          0  redo size
        417  bytes sent via SQL*Net to client
        457  bytes received via SQL*Net from client
          1  SQL*Net roundtrips to/from client
          1  sorts (memory)
          0  sorts (disk)
          0  rows processed

B. Polarski
Oracle DBA

--
http://www.freelists.org/webpage/oracle-l

Received on Thu Oct 19 2006 - 06:52:03 CDT