DataPump Import Parameter REMAP_SCHEMA Does Not Import To Default Tablespace
(Doc ID 796671.1)
Last updated on JANUARY 30, 2022
Applies to:
Oracle Database - Enterprise Edition - Version 10.2.0.4 and laterOracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Information in this document applies to any platform.
Symptoms
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-39083: Object type TABLE failed to create with error:
ORA-959: tablespace '<TABLESPACE_NAME>' does not exist
ORA-959: tablespace '<TABLESPACE_NAME>' 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?
Changes
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |