Import DataPump: Transport Tablespace Fails with ORA-39123 and 29344 (Failed to match owner SYS)
(Doc ID 294992.1)
Last updated on JANUARY 30, 2022
Applies to:
Oracle Database - Personal Edition - Version 10.1.0.2 to 10.1.0.5 [Release 10.1]Oracle Database - Enterprise Edition - Version 10.1.0.2 to 10.1.0.5 [Release 10.1]
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Information in this document applies to any platform.
NOTE: In the images and/or the document content below, the user information and data used represents fictitious data. Any similarity to actual persons, living or dead, is purely coincidental and not intended in any manner.
Symptoms
Oracle10g Import DataPump fails to transport a tablespace back into a database. The output in the log file shows:
Changes
1. You recently upgraded the database to Oracle10g, Release 1, 10.1.0.x.0 and are using Export DataPump and Import DataPump.
2. You recently created an object owned by SYS in the tablespace that is transported, and dropped that object. Instead of SYS, the dropped object could also have been owned by ORDSYS, MDSYS, CTXSYS, ORDPLUGINS, LBACSYS, XDB, SI_INFORMTN_SCHEMA, DIP, DMSYS, or DBSNMP (these are non-exportable users).
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 |