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.