Re: Importing user in an other tablespace

Do a USER level export of the source schema. Create the new schema in the target database. Make sure that the schema/user does not have UNLIMITED_TABLESPACE, RESOURCE, or DBA. Grant CONNECT role. Grant CREATE_PROCEDURE, CREATE_TYPE, and CREATE_TRIGGER system privs. Set the default tablespace to where you want the objects to go and give the schema UNLIMITED quota on it. Do a USER level import and specify IGNORE=Y. This has always worked for me. If you have LOB's do a FULL export at the source and USER level at the target.

dale_at_databee.com (Dale Edgar) wrote in message news:<3c500289.2554631_at_news.btclick.com>...
> Hi Frank
>
> On Thu, 24 Jan 2002 12:18:25 +0100, "Frank Demuynck"
> <frank.demuynck_at_entelec.be> wrote:
>
> >I want to move a user who is created in the tablespace users to an other
> >tablespace on an other server.
> > [...stuff snipped...]
> >So the import want to create the table in the tablespace users who is
> >offline
> >But I want that the import create the tables in the new tablespace
>
> The export file has the storage clause and tablespace information
> imbedded within it. You will have to pre-create the objects that are
> to go into the new tablespace and then import with the ignore=Y
> option.
>
> If you don't wish to find and modify all the DDL by hand you should
> consider getting the free DBATool software. The DBATool is designed
> to read an export file and strip off (or replace) tablespace and
> storage clause information. It is a trival task to have the DBATool
> generate runnable SQL scripts of your DDL without the tablespace and
> storage clause information.
>
> The DBATool can be found at: http://www.databee.com/dt_home.htm
>
> Thanks
> Dale Edgar
> Net 2000 Ltd.
> Dale_at_DataBee.com
Received on Thu Jan 24 2002 - 19:50:06 CET