DataPump Import Parameter REMAP_SCHEMA Does Not Import To Default Tablespace
Last updated on MAY 23, 2013
Applies to:Oracle Database - Enterprise Edition - Version 10.2.0.4 and later
Information in this document applies to any platform.
***Checked for relevance on 23-May-2013***
DataPump import using the parameter REMAP_SCHEMA does not import the objects to the user's default tablespace in target database.
If target database does not have the tablespaces as in source, it fails with the below error:
ORA-959: tablespace 'XYZ' does not exist
The import is looking for the same tablespaces as in source instead of using the users default tablespace in the destination.
How to move all the objects to the user's default tablespace after import?
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms