Home » RDBMS Server » Server Utilities » impdp changes the ownership of a DBA_JOB (10.2.0.4 on Sun Solaris 10)
impdp changes the ownership of a DBA_JOB [message #400959] Thu, 30 April 2009 12:38 Go to next message
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 #400961 is a reply to message #400959] Thu, 30 April 2009 13:02 Go to previous messageGo to next message
BlackSwan
Messages: 25046
Registered: January 2009
Location: SoCal
Senior Member
> I imported as SYSTEM
That was the wrong thing to do.

Why did you contaminate SYSTEM with application objects?
Re: impdp changes the ownership of a DBA_JOB [message #400963 is a reply to message #400959] Thu, 30 April 2009 13:05 Go to previous messageGo to next message
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 #400967 is a reply to message #400959] Thu, 30 April 2009 13:12 Go to previous messageGo to next message
BlackSwan
Messages: 25046
Registered: January 2009
Location: SoCal
Senior Member
Unfortunately Oracle does not provide the ability to change owner of JOB.
At a minimum new JOB must be created as new owner.
Removal of old JOB is optional.
Re: impdp changes the ownership of a DBA_JOB [message #400970 is a reply to message #400967] Thu, 30 April 2009 13:29 Go to previous messageGo to next message
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
Re: impdp changes the ownership of a DBA_JOB [message #486040 is a reply to message #400970] Mon, 13 December 2010 03:34 Go to previous message
mjsadiq
Messages: 1
Registered: December 2010
Junior Member
Anyway, this doesn't happen for scheduler jobs.
Previous Topic: Loader - duplicated rows
Next Topic: filesize in expdp /impdp
Goto Forum:
  


Current Time: Thu Dec 08 14:32:54 CST 2016

Total time taken to generate the page: 0.08926 seconds