Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
![]() |
![]() |
Home -> Community -> Usenet -> c.d.o.server -> Re: Partition Indexes
Think I have traced the problem. Though I'm not sure why it happens.
Result:
Fast Full Index Scan on the local parititioned indexes for col1 using
partition iteration. On our system, that results in 3,023,064 blocks being
read (according to TKPROF).
Elapsed time: 414 seconds
Result:
Index Range Scan per local paritioned index per partition. On our system
that is 487 blocks being (again according to TKPROF).
Elapsed time : 0.42 seconds
Question:
Is this an Oracle 8.1.7 bug*? It it a known bug? Any suggestions how to work
around this problem (it severely degrades the performance of certain
queries)
Comments, suggestions and German beer appreciated.
-- Billy * HP-UX 11 running 32bit 8.1.7Received on Tue Sep 10 2002 - 04:09:42 CDT
![]() |
![]() |