IMPDP Reports ORA-942 and ORA-39083 During Importing Schema Objects
(Doc ID 750783.1)
Last updated on DECEMBER 08, 2023
Applies to:
Oracle Database Cloud Schema Service - Version N/A and laterOracle Database Exadata Express Cloud Service - Version N/A and later
Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Backup Service - Version N/A and later
Information in this document applies to any platform.
NOTE: In 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
During DataPump import of schema objects (such as triggers, functions, etc.), errors ORA-39083 and ORA-942 occur when the object code contains hard coded schema references and the schema does not exist in the target database.
The parameter REMAP_SCHEMA will not prevent this issue, like demonstrated in next example:
TEST CASE
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 |
| Cause |
| Solution |