If you specify ignore=y in your import the table will get created in the schema's default tablespace. Just make sure that the default tablespace is the one that you want to use. Otherwise create the table the way you want in the proper tablespace then import with ignore=y.
It's a problem with quota. Just check you have quota on your default tablespace.
gandolf : No need for ignore=y when importing to default default tablespace. Oracle automatically imports to default tablespace if the tablespace defined with export dumpfile is not present in targer database.
Originally posted by nagarjuna It's a problem with quota. Just check you have quota on your default tablespace.
gandolf : No need for ignore=y when importing to default default tablespace. Oracle automatically imports to default tablespace if the tablespace defined with export dumpfile is not present in targer database.
You are wrong and GANDOLF is right.
For a single tablespace clause (say a non-partitioned table create), IMP will redirect object creation to the default tablespace for the user if the specified tablespace does not exist.
For DDL with potentially multiple tablespace clauses (say, a partitioned table create as we have in our case) Oracle will give an ORA-00959. When there are multiple tablespace clauses, IMP cannot determine which tablespace is missing and changing all tablespace clauses to the default is not a plausible solution.
Oracle Certified Master
Oracle Certified Professional 6i,8i,9i,10g,11g
email: ocp_9i@yahoo.com
Disclaimer: Advice is provided to the best of my knowledge but no implicit or explicit warranties are provided. Since the advisor explicitly encourages testing any and all suggestions on a test non-production environment advisor should not held liable or responsible for any actions taken based on the given advice.
Bookmarks