Re: Import questions

Oracle considers the unique constraints to be part of the table. But as a unique constraint is an index they show up as such.

You are on the right track all you need is steps 1 and 2 as you indicated but add constraints=y to your indexfile create and the index.sql will include the statements to re-create all indexes unique/pk constraints included. Then you won't need to re-run the import to create the constraints... and you can move you constraints to another tablespace (which is what I assume you are trying to do).

Regards

Fraser McCallum
MVP Oracle
www.brainbench.com

"Vikas Agnihotri" <onlyforposting_at_yahoo.com> wrote in message news:77e87b58.0105240901.4078c580_at_posting.google.com...
> Doing a full import from a 'exp full=y'
>
> I pre-created my tablespaces.
>
> Now I want to import everything except the indexes, run the indexfile
> and then edit the indexfile to add (parallel, nologging, compress) and
> create indexes.
>
> I did the following
>
> 'imp full=y indexes=n'
>
> Strangely, this seems to have created some indexes also. Looking
> closer, they seem to be the indexes associated with unique/pk
> constraints.
>
> Questions:
>
> 1. How do I do imp such that NO indexes get created? 'imp full=y
> indexes=n constraints=n'?
>
> 2. If so, then I then do a 'imp full=y indexfile=index.sql', edit
> index.sql and run it to create indexes.
>
> Do I then need to run 'imp full=y indexes=n constraints=y' to create
> all my constraints? Will the PK/unique constraints automatically use
> the existing indexes to enforce the constraints?
>
> Would appreciate help from someone who has done this sort of thing
> before.
>
> Thanks for your help.
Received on Thu May 24 2001 - 16:19:53 CDT