Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
Home -> Community -> Usenet -> c.d.o.server -> Re: Problems on copying a database user from one tablespace to another on the same instance
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_at_duke.edu Marc Staudacher <marcst_at_gmx.ch> wrote in message news:913fkm$q1i$1_at_bw107zhb.bluewin.ch...Received on Tue Dec 12 2000 - 13:48:18 CST
> 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_at_faw.uni-linz.ac.at> wrote in message
> news:3a33d96d_at_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
> >
> >
> >
>
>