Re: job ownership during schema imp/exp changes

NetComrade wrote:
> Is there are any way to prevent jobs from being imported under wrong
> username (SYS) when schema exp/imp is being done (e.g. schema
> movement?)
>
> I suspect this has to do with user_id's not matching..
>
> Thanks.
> .......
> We run Oracle 9.2.0.6 on RH4 AMD
> remove NSPAM to email

If the intent is to avoid importing a job when you import other things owned by the original user, you can either drop the job after import, or pre-create a dummy job in the target database using dbms_jobs.isubmit with the same job number as the job in the source. This is because the imported job would take the same job number and fail to be imported if the number is already taken.

Whoever imports the schema owns the job. If your intent is to create a job in the target database under the original user's ownership (as shown under dba_jobs.log_user and priv_user but not schema_user), you still do the same. Then recreate the job under the correct schema. Dbms_job.user_export makes this a little easier. See Metalink 322797.999.

Why not temporarily allow the user instead of SYS to import? Is there anything only SYS can do (like row level security stuff)?

Yong Huang Received on Wed Jan 18 2006 - 22:54:45 CST