Re: EXP/IMP to a different tablespace: has anyone been able to solve this?

On Oct 24, 6:36 am, arr..._at_inbox.com wrote:
> Followed all writeups I've read so far to come with the following:
>
> ----------------------------------------------
>
> alter user ${dest_schema} quota 0 on ${src_tablespace};
>
> alter user ${dest_schema} quota unlimited on ${dest_tablespace};
>
> imp file=${exp_file} ignore=Y fromuser=${src_schema} touser=$
> {dest_schema}
>
> ----------------------------------------------
>
> It does indeed create new objects in a new tablespace, but as soon as
> there's at least 1 row in the export file, it stubbornly attempts to
> go back to the src_tablepace (original user's tablespace data was
> exported from) and generates ORA-01536: space quota exceeded for
> tablespace error.
>
> Is there a clean solution, or each time I need to mess with renaming
> all tablespaces before imp and then renaming them back after imp?

from a very remote corner of my memory:
I think you need to not use a dba account to run the exp/imp. Then it will take into account the default tablespace of "touser" and use only that.

But like I said: very remote corner... Received on Wed Oct 24 2007 - 07:02:44 CDT