IMPDP doesn't remap Database Jobs to new User Schema
(Doc ID 1122424.1)
Last updated on APRIL 03, 2020
Applies to:Oracle Database - Enterprise Edition - Version 10.1.0.2 to 18.104.22.168 [Release 10.1 to 11.2]
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.
When you export/import a user schema which contains a database job, the Data Pump Import (Impdp) doesn't remap the job to a new schema when REMAP parameter is used. The job is still owned by the original user while other objects such as the PLSQL code of the database job are owned by the new user.
Sequence of events leading to the problem:
- Submit a job using DBMS_JOB.SUBMIT
- Export the schema using Data Pump Export (expdp)
- Import the schema into a different user schema by using REMAP
The following test case illustrates this in more detail:
Schema data (user U1) was correctly remapped to new user U2, however the job is still owned by non-existing user U1.
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