Btw, if you hint your query to use full table scans now or not to use your bitmap index (this means optimizer won't consider accessing your "parallel" index), the query will run in serial, because optimizer only sees noparallel objects. It works the other way too, that if your table is parallel, but it's contents are accessed from a noparallel index, optimizer won't take the parallel degree of underlying table into account... Tanel. ----- Original Message ----- From: "Michael McMullen" <ganstadba@xxxxxxxxxxx> To: <oracle-l@xxxxxxxxxxxxx> Sent: Tuesday, August 03, 2004 8:41 PM Subject: Re: parallel execution on partitioned tables (was: Oracle 9.2.0.5 "10046" Tracing ...) > Well now I can go home because I've learned something today. Never looked at > degree in dba_indexes. I create all of my indexes in parallel which I guess > automatically puts as degree = 'DEFAULT'. I have only seen this effect on my > partitioned tables. This is good, time for some serious testing. > > Thanks > Mike ---------------------------------------------------------------- Please see the official ORACLE-L FAQ: http://www.orafaq.com ---------------------------------------------------------------- To unsubscribe send email to: oracle-l-request@xxxxxxxxxxxxx put 'unsubscribe' in the subject line. -- Archives are at //www.freelists.org/archives/oracle-l/ FAQ is at //www.freelists.org/help/fom-serve/cache/1.html -----------------------------------------------------------------