Re: import question

Cameron,

As long as you are using tablespaces with the same names in both databases you will be OK.

What ignore=y tells import is to ignore object creation errors. Thus it will not get upset when it discovers your tablespaces already exist and will skip to whatever action is next in your dump file. This means it will not recreate existing tablespaces, tables, indexes etc if it finds them. Also your datafiles will remain untouched as they are part of the tablespace creation statement in an import.

If a tablespace of the same name as an object previously resided in exists then import will stick it there. If no tablespace of the same name exists then import will try to stick in a users default tablespace. The only area I could see where your plan would come undone would be if no tablespace of the same name as the users default or the objects previous existed.

All of this is of course as long as you haven't set destroy=y which tells Oracle to overwrite the datafiles and tablespaces.

Kind Regards

Fraser McCallum
MVP Oracle Administration
www.brainbench.com

"Cameron Abbott" <cvabbott_at_altavista.com> wrote in message news:9ses8j$len$1_at_bcarh8ab.ca.nortel.com...
> Hi All,
>
> I have a database and have imported all the data into this new database
from
> another database. I only exported the data of two users and mported it.
> This created all the tables,data,sequences and indexes. Has a test I want
> to drop the two users to remove all their objects, then recreate the
users.
> My question is, if I do a full export and on the import set ignore=y, will
> the import over write the information in the new database for tablespaces
> and datafiles with the tablespace and datafile information in the old
> database? I do not want the database structure to change, I have made
many
> modifications to the new database to increase its size because the old one
> was too small and I didn't have the disk space to make it larger.
>
> If it do over write, what will happen when the directory structure of the
> old database does not exist on the new one?
>
> Thanks
>
> Cameron
>
>
Received on Thu Nov 08 2001 - 16:02:26 CST