Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> c.d.o.misc -> Re: Using INDEXES=N in imp

Re: Using INDEXES=N in imp

From: Mark D Powell <mark.powell_at_eds.com>
Date: 13 May 2002 06:52:33 -0700
Message-ID: <178d2795.0205130552.1d493c99@posting.google.com>


Sybrand Bakker <postbus_at_sybrandb.demon.nl> wrote in message news:<09hudu0q11g48ennedrpob8kel6gferu3s_at_4ax.com>...
> On Sun, 12 May 2002 23:45:07 -0400, C Chang <cschang_at_maxinter.net>
> wrote:
>
> >I put INDEXES=N in imp script as
> >imp sys/password d:\dump_file.dmp fromuser=me touser=me indexes=n
> >commit=y d:\dump_file.log
> >aftr the import has finished, I still saw the old indexes ( using the
> >DBA studio), Why?
> >
> >C Chang
>
>
> Indexes=n doesn't apply to PK and unique constraints
>
> Regards
>
>
> Sybrand Bakker, Senior Oracle DBA
>
> To reply remove -verwijderdit from my e-mail address

Chang, if you do not want to import the indexes I generally find it better to make the exp using constraints=n indexes=n rather than use the same two parameters on the import. If you make a second export using rows=n but with indexes=y constraints=y then imp this file after the other one you can bring any missing objects like FK and overlooked indexes to be sure you have everything. In the case of a full exp this provides a means to bring public objects when you pre-allocate the user objects as in the case of where you relocated them.

Received on Mon May 13 2002 - 08:52:33 CDT

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US