Re: exchange partition and transport tablespace with unique constraints

The saga continues... not only did I verify that you can import and exchange to a table partition that has the constraints in "enable novalidate rely" mode. I just took a new partition and exchanged it and transported (exp) it while all of the partitioned table constraints where "enable novalidate rely".. even the unique constraint (which is now based on a non-unique index) let me do this.  What is going on here? Is there any guide explaining what you can and can't do with exchanges and transportable tablespaces (both exp and imp) on partitioned tables with PK, FK, and unique constraints? It seems the following applies with a partitioned table with constraints (tabp part1) and a similar nonpartitioned table without constraints (tabx):

1. Can exchange tabp part1 with tabx and back again with constraints DISABLED.. and you can transport. (duh!)
2. Can exchange tabp part1 with tabx with constraints ENABLE VALIDATE, but you can't exchange them back without disabling constraints... and you can't transport these "not self contained" tablespaces.
3. Can exchange tabp part1 with tabx and back again with constraints ENABLE NOVALIDATE... but, you can't transport: not self contained.
4. Can exchange tabp part1 with tabx and back again with constraints ENABLE NOVALIDATE RELY... AND, you can transport them.

I've run through these scenarios to confirm this... I'm not sure if there something I'm overlooking in this mix (like what if you set the tablespaces as read only... before the exchange)? If there are no adverse implications to #4... what a way to go... keep the constraint in force at all times and still be able to exchange out and transport your old partitions. Anybody see a flaw with this plan?

john.

john.summers_at_medtronic.com (John Summers) wrote in message news:<5d76b757.0204100839.770e2695_at_posting.google.com>...
> Thanks for the info... I recreated my index as "not unique" and went
> about my business. I'm now working on what to do with these
> transported tablespace datafiles (which total 10G+ for each month).
> The fact that you can import them from just about anywhere is nice. I
> freed up a volume for this purpose... did the import and then, with
> all my main partitioned tables constraints in "enabled novalidate
> rely" mode, I did the exchange partition. And it worked... ?
> The problem is, I originally had to disable all of these partitions to
> get the exchange and export to work in the first place. How is it that
> I can now put them back without needing to disable anything? I'm lost
> again... although this would be a nice feature if true, but I can't
> figure out why this is working (and that may mean that it is not).
>
> John.
Received on Thu Apr 11 2002 - 18:06:41 CDT