Re: enable/disable constraint, rebuild index

1. Capture the storage parameters before disabling the primary/unique constraint.
2. Supply them when enabling the constraint. It's important to name the constraint so the index will have a meaningful name (otherwise you get SYS_Cxxxxx). Also specify the tablespace in which to build the index. Remember that the default is to use the user's default tablespace, and the default storage parameters for that tablespace. Usually, that's not what you want. -- - Dan Clamage http://www.telerama.com/~dclamage If you haven't crashed the Server, you haven't been trying hard enough.

Winnie Liu <poohland_at_hotmail.com> wrote in article <6rt3kg$5sm_at_dfw-ixnews9.ix.netcom.com>...
> Hi everyone,
>
> I learn recently that when you disable the primary key and unique key
> constraint. The indexes associated with it are gone. When you enable the
> constraint, Oracle will build the index on the user's default tablespace
> instead the of the tablespace that you specific when you create the
primary
> key/unique constraint.
>
> How about rebuilding index? Is it going to the user default or the
> tablespace that index resign in? (I really hope that it is the second
one...
> I always think that it will go to the tablespace which I create the index
> instead of the default tablespace! =<)
>
> Thanks everyone!
>
> Winnie
>
>
>
Received on Thu Aug 27 1998 - 17:14:52 CDT