Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
Home -> Community -> Usenet -> c.d.o.server -> Re: Preventing jobs from being imported
Connor McDonald <connor_mcdonald_at_yahoo.com> wrote in message news:<4118C3B3.1970_at_yahoo.com>...
> Paul Drake wrote:
> >
> > hboswel1_at_bellsouth.net wrote in message news:<cuifh0duak1uhls5m00d2pbjbrbi6erkc3_at_4ax.com>...
> > > On Mon, 09 Aug 2004 11:09:19 -0500, Turkbear <john.g_at_dot.spamfree.com>
> >
> > this should tidy it up - might have a typo, didn't eat dinner yet and
> > brain is shutting down ...
> >
> > connect imported_user/pword
> >
> > begin
> > for rec in (select job from user_jobs)
> > loop
> > execute immediate (exec dbms_job.remove(rec.job));
> > end loop;
> > end for;
> > end;
> >
> > commit;
> >
> > that won't work if you're importing as a different user.
> > e.g. running imp as system, the system account would own the jobs.
> > you'd have to connect as the owner of the dbms_jobs.
> >
> > -bdbafh
>
> its also worth setting job processes to zero before the
> import...otherwise they can start before you get a chance to blow them
> away.
>
>
> --
> Connor McDonald
> Co-author: "Mastering Oracle PL/SQL - Practical Solutions"
> ISBN: 1590592174
>
> web: http://www.oracledba.co.uk
> web: http://www.oaktable.net
> email: connor_mcdonald_at_yahoo.com
>
> Coming Soon! "Oracle Insight - Tales of the OakTable"
>
> "GIVE a man a fish and he will eat for a day. But TEACH him how to fish,
> and...he will sit in a boat and drink beer all day"
funny, all the things that pop into your head, after you hit the "send" button. thanks for the follow up. thought of it after I posted, didn't follow it up me self.
my copy of TOTOT just arrived. Sleep, or read? I think it will work itself out.
-bdbafh Received on Wed Aug 18 2004 - 01:13:18 CDT