Re: Building a Partitioned Primary Key index on a VLDB?

By equipartition I assume you mean a local index. Since it should be a fully prefixed local index to be the PK index, then I am
a little surprised that your strategy does not work.

You might, however work on this idea (which I have not tested).

Create the partitioned table without any indexes Load the data into it

Exchange every partition for a matching empty table Create a unique local index on the partitioned table Create unique indexes on each of the exchanged out partitions Exchange each table back into the partitioned table using the:

        including indexes without validation
option.
Create the primary key constraint (which should use the existing unique index).

Jonathan Lewis

doid_at_usa.net wrote in article
<01bdf167$cc8bee50$0300a8c0_at_WORKSTATION>...
>
>
>
> For logistical reasons, we need to move the data before we begin
> building
> indexes. We wish to use an equipartitioned index for the primary
key
> of the
> new table.
>
> The problem is this: in my tests, I'm having difficulty finding a
> way to
> build the primary key index without doing a full table scan. If
this
> weren't
> a primary key, I could begin by making all partitions of the index
> UNUSABLE,
> then rebuild the index one partition at a time. The problem I'm
> having is
> that Oracle seems to insist that all partitions of a Primary Key
> index be
> usable.
Received on Wed Oct 07 1998 - 09:58:10 CDT