| impdp changes the ownership of a DBA_JOB [message #400959] |
Thu, 30 April 2009 12:38  |
Orna
Messages: 62
Registered: November 2008
|
Member |
|
|
Hi
When I am exporting a schema that own several DBA_JOBS using expdp, and then importing it into another database - the DBA_JOB change ownership to the schema I used for the import.
For example :
the log_user,priv_user and schema_user used to be schema 'A'
but after the impdp, assuming I imported as SYSTEM, the log_user,priv_user and schema_user are now SYSTEM !.
Is this an expected behavior ?
How can I avoid it ?
the job will fail executing as SYSTEM , and I need to manually create it as user A again
thanks in advance
Orna
|
|
|
|
|
|
| Re: impdp changes the ownership of a DBA_JOB [message #400963 is a reply to message #400959] |
Thu, 30 April 2009 13:05  |
Orna
Messages: 62
Registered: November 2008
|
Member |
|
|
Hi
That was NOT my intention
I only imported AS system
imdp system dumpfile=... logfile... schemas=A
All the objects went to schema A , not to SYSTEM.
Only the Jobs , for some reason , were created under SYSTEM.
I always use SYSTEM to import. many times I import multiple schemas and I need a privileged user.
Again - no objects are created under SYSTEM ( excluding the jobs - and that was my original question )
Orna
|
|
|
|
|
|
| Re: impdp changes the ownership of a DBA_JOB [message #400970 is a reply to message #400967] |
Thu, 30 April 2009 13:29 |
Orna
Messages: 62
Registered: November 2008
|
Member |
|
|
thank you for that
I think its quite a limitation to the expdp/impdp utility.
its strange that a job is the only entity that cannot be copied over using the exp/imp
I need to check it - but I wonder if this is also true for dba_scheduler_jobs - the new generation of dba_jobs
Orna
|
|
|
|
|
|
] 
Blog
Search
Help
Members
Register
Login
Home
