It's certainly an option to consider.
In fact it's always worth considering having
different degrees of parallelism on the index
and the table when using partitioned tables.
There may be cases where (for example)
a parallel degree 10 scan of a table and a
parallel degree 5 index range scan perform
at about the same speed, but one is more
desirable than the other for some application
dependent reason.
--
Jonathan Lewis
Yet another Oracle-related web site: http://www.jlcomp.demon.co.uk
Practical Oracle 8i: Building Efficient Databases
Publishers: Addison-Wesley
Book bound date: 8th Dec 2000
See a first review at:
http://www.ixora.com.au/resources/index.htm#practical_8i
More reviews at: http://www.jlcomp.demon.co.uk/book_rev.html
Lynux wrote in message <8vmbe9$hsk2_at_imsp212.netvigator.com>...
>Actually, we experience this result when we are building a local index
>onto a partitioned table. The 'multiple extents' are significant in the
>dba_extents. However, you have given me a great hints. Maybe you are
>right, we can take the parallelism benefit on tables' selection using
>index with degree > 1 and do only single extent for insert/update (As I
>need to check). When building or re-building the index, we need to
>temporarily change it into degree 1 (noparallel) first. That is, our
>DBA should take a caution on the degree of these index!
>Please correct me if I am wrong! Thank You
>
Received on Fri Nov 24 2000 - 14:57:21 CST
