Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>The problem has to do with the CLOB columns. It seems that the imp tool cannot rewrite the create statement to use another tablespace.</p> <p>Source: <a href="http://asktom.oracle.com/pls/asktom/f?p=100:11:0::::P11_QUESTION_ID:66890284723848" rel="nofollow noreferrer">http://asktom.oracle.com/pls/asktom/f?p=100:11:0::::P11_QUESTION_ID:66890284723848</a></p> <p>The solution is: Create the schema by hand in the correct tablespace. If you do not have a script to create the schema, you can create it by using the indexfile= of the imp tool.</p> <p>You do have to disable all constraints your self, the oracle imp tool will not disable them. </p> <p>After that you can import the data with the following command:</p> <blockquote> <p>imp b/*** file=oracledump.dmp log=import.log fromuser=a touser=b statistics=none ignore=y</p> </blockquote> <p>Note: I still needed the statistics=none due to other errors.</p> <p><strong><em>extra info about the data pump</em></strong></p> <p>As of Oracle 10 the import/export is improved: the data pump tool ([<a href="http://www.oracle-base.com/articles/10g/OracleDataPump10g.php][1]" rel="nofollow noreferrer">http://www.oracle-base.com/articles/10g/OracleDataPump10g.php][1]</a>)</p> <p>Using this to re-import the data into a new tablespace:</p> <ol> <li><p>First create a directory for the temporary dump:</p> <blockquote> <p>CREATE OR REPLACE DIRECTORY tempdump AS '/temp/tempdump/';<br> GRANT READ, WRITE ON DIRECTORY tempdump TO a;</p> </blockquote></li> <li><p>Export:</p> <blockquote> <p>expdp a/* schemas=a directory=tempdump dumpfile=adump.dmp logfile=adump.log</p> </blockquote></li> <li><p>Import:</p> <blockquote> <p>impdp b/* directory=tempdump dumpfile=adump.dmp logfile=bdump.log REMAP_SCHEMA=a:b</p> </blockquote></li> </ol> <p>Note: the dump files are stored and read from the server disk, not from the local (client) disk</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload