From: "John Jones" <john.jones@duke.edu>
Newsgroups: comp.databases.oracle.server
Subject: Re: Problems on copying a database user from one tablespace to another on the same instance
Date: Tue, 12 Dec 2000 14:48:18 -0500
Organization: Duke University, Durham, NC, USA
Lines: 65
Message-ID: <915vfk$9er$1@news.duke.edu>
References: <3a33d96d@alijku02.edvz.uni-linz.ac.at> <913fkm$q1i$1@bw107zhb.bluewin.ch>
NNTP-Posting-Host: soleri.oit.duke.edu
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 5.00.2314.1300
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300


There is an order to import.  First, it looks at the tablespace that it came
from, if it exists on the import side, that is were it will put it,  if it
is not there then it will put it in the default tablespace of the user being
imported into.  Just precreate the tables in any tablespace and use the
ignore=y parameter in the import.

--
John Jones
Senior Oracle DBA
Duke University, OIT
john.jones@duke.edu
Marc Staudacher <marcst@gmx.ch> wrote in message
news:913fkm$q1i$1@bw107zhb.bluewin.ch...
> Another way to do the same:
> If you set the IGNORE-parameter (IGNORE=Y) in your import-parfile, you
 could
> precreate the whole scheme in the other tablespace. Then the
 DDL-statements
> in your export will be ignored (though firing a warning).
>
> regards,
> Marc Staudacher
>
> "Peter Kroiss" <pk@faw.uni-linz.ac.at> wrote in message
> news:3a33d96d@alijku02.edvz.uni-linz.ac.at...
> > I tried to export a user with
> > BUFFER=8192
> > FILE=G:\export.dmp
> > COMPRESS=Y
> > GRANTS=Y
> > INDEXES=Y
> > ROWS=Y
> > CONSTRAINTS=Y
> > LOG=G:\export.log
> > OWNER=(USER1)
> > RECORDLENGTH=8192
> >
> > and then reimport the data into a new user on a new tablespace with
> > BUFFER=8192
> > FILE=G:\export.dmp
> > SHOW=N
> > IGNORE=N
> > GRANTS=N
> > INDEXES=N
> > ROWS=Y
> > LOG=g:\import.log
> > DESTROY=N
> > FULL=N
> > FROMUSER=(USER1)
> > TOUSER=(NEWUSER)
> > RECORDLENGTH=8192
> > COMMIT=N
> >
> > The problem is that the import always creates the tables in the the
> > tablespace from user1 and not in the default-tablespace
> > of the new user (NEWUSER).
> >
> > Peter
> >
> >
> >
>
>