Originally posted by jmodic
When you disable a PK constraint, by default its underlying index is dropped. The definition of constraint remains in a dictionary, while the definition of its index is wiped out, Oracle no longer knows in which tablespace the index under that PK was created. So after you enable that PK again, Oracle has to create a fresh new index for it. In which tablespace will that index be created? Well, as allways, if you don't specify that explicitely, it will be created in user's default tablespace, regardles of where it's parent table resides.

So if you don't want that index to be in the default tablespace, tell to Oracle where you want it:
Code:
ALTER TABLE n_contact_history
ENABLE VALIDATE CONSTRAINT pk_c_contact_history
USING INDEX TABESPACE mart;
Ah, I learn something new every day...

Bazza