Re: Jobs stills executed after OEM crash

"Robert" <cookie - remove - @tref.nl> wrote in message news:bou8qi$c44$1_at_reader11.wxs.nl...
> Ed Stevens wrote:
>
> > On Wed, 12 Nov 2003 20:29:21 +0100, Robert <cookie - remove -
> > @tref.nl> wrote:
> >
> >>Hi there,
> >>
> >>
> >>
> >>I have an 8.1.7 DB running on NT4
> >>We use OEM from 9.0.2 on a W2k box.
> >>
> >>I have created a job which calls a .cmd file on the db server once at
> >>night. This script logs on to the DB and does a "backup controlfile to
> >>trace" Afterwards the backup controlfile is copied to another machine.
> >>
> >>I don't like loosing my controlfiles so it is to be safe.
> >>
> >
> > As an aside to your question, which others have answered correctly .
> > . .
> >
> > Most of us don't like losing *any* files related to the db. Is this
> > the only backup you're doing?
> >
> >
> >
> > <snip>
>
>
> LOL : No of course not.
> We do a cold backup every night (datafiles, controlfiles, pfile, etc)
> Every first saterday of the month we do a total OS image of the machine.
> It's just that if something gets screwed in the controlfile dept (i know
we
> have tapes for at least 14 days with controlfiles ) i like to have a
> backuped controlfile. It may be overprotection but hey, better be safe
then
> sorry. It's only 1 minute execution and a file of aprox. 5M.
>
> But thanks for your care !!
>
> I saw the job.q file and suspected this file to be the local job queue.
> It a binary file so i couldn't read / edit it.
>
> Do you know if i can safely delete this file without crashing the
> intelligent agent?

No you can't.

If you try deleting it, you'll get a 'sharing violation' error in Windows, meaning the file is in use and can't be deleted at all.

If you stop the agent, delete the file, and then re-start the agent, that will work fine.

Regards
HJR Received on Wed Nov 12 2003 - 15:32:32 CST