Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
Home -> Community -> Mailing Lists -> Oracle-L -> RE: imp issue...very confusing!
precreate the destination tables and indexes on the target schema,
then import with ignore=y
George
You Have The Obligation to Inform One Honestly of the risk, And As a Person You Are Committed to Educate Yourself to the Total Risk In Any Activity! Once Informed & Totally Aware of the Risk, Every Fool Has the Right to Kill or Injure Themselves as They See Fit!
-----Original Message-----
From: Denham Eva [mailto:EVAD_at_TFMC.co.za]
Sent: Tuesday, July 13, 2004 4:33 PM
To: oracle-l_at_freelists.org
Subject: imp issue...very confusing!
Hello Gurus,
Here is the situation, I have a Oracle 7.3.4 dump, which am importing
into a Oracle 9.2 server, both Windows platforms.
I created a new user "schema" for the data, with it's own tablespace
etc.
No fancy imp parameters other than fromuser, touser.
Here is my problem, the fromuser does already exist on the server with its data from the 7.3 server. So the import is now happily importing the data but into the fromuser tablespace and not into the touser's tablespace as I had wanted it to. The touser is now the owner, but naturally the tablespace of fromuser has began to grow huge.
Why is this? I have rtfm-ed the docs. I don't really get any answers as it speaks of transport_tablespace, but I don't think this is quite the option I would require.
Has anyone got any ideas?
Many Thanks
Denham
The views expressed in this email are, unless otherwise stated, those of the author and not those of the FirstRand Banking Group or its management. The information in this e-mail is confidential and is intended solely for the addressee. Access to this e-mail by anyone else is unauthorised. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted in reliance on this, is prohibited and may be unlawful. Whilst all reasonable steps are taken to ensure the accuracy and integrity of information and data transmitted electronically and to preserve the confidentiality thereof, no liability or responsibility whatsoever is accepted if information or data is, for whatever reason, corrupted or does not reach its intended destination.