Re: Physical reads on table very high.

From: Ethan Post <epost1NOepSPAM_at_yahoo.com.invalid>
Date: 2000/07/13
Message-ID: <02eace00.04b29b5e@usw-ex0105-037.remarq.com>#1/1

Ok here is execution plan:

SQL> SELECT * FROM SVMB733.F986110 WHERE ( JCJOBQUE = 'QB7331 '
2 AND JCJOBSTS = 'D ' AND

  3  JCEXEHOST = 'hq-asprd                                '
  4   AND JCFUNO = 'UBE '
  5   AND JCPRTQ = '7100      ' );

Execution Plan

0
SELECT STATEMENT Optimizer=CHOOSE (Cost=831 Card=3112 Bytes=1191896)

          1                  0

TABLE ACCESS (FULL) OF 'F986110' (Cost=831 Card=3112 Bytes=1191896)

So it is obviously using full table scan but here is the index I created:

create index jdeF986110_01 on F986110 (JCJOBQUE, JCJOBSTS, JCEXEHOST, JCFUNO, JCPRTQ)
tablespace svmb733i;

Same columns as in the SQL statement why doesn't the optimizer see that this is the best way to go???

Thanks,
Ethan

Got questions? Get answers over the phone at Keen.com. Up to 100 minutes free!
http://www.keen.com Received on Thu Jul 13 2000 - 00:00:00 CDT