Re: Jobs submitted under OEM start but do not finish

davepashby.google_at_solmanoz.freeserve.co.uk (pashda) wrote in message news:<334c7316.0306040153.6c1c4c79_at_posting.google.com>...
> magil_ru_at_yahoo.com (VM) wrote in message news:<e92668ff.0306032211.22ec253f_at_posting.google.com>...
> > davepashby.google_at_solmanoz.freeserve.co.uk (pashda) wrote in message news:<334c7316.0306030145.4c0ffd91_at_posting.google.com>...
> > This is exactly why I stopped using OEM.
> >
> > I wouldn't go that route if you decided to use OEM then make it work -
> > open a TAR with Oracle Support and get them to fix the problem. Did
> > it ever work? Adding another bolt-on APP on top of OEM is just going
> > to add one more weak link to the chain that's already falling apart.
> >
> > Regards,
> >
> > Vitaliy
> > DBAToolZ.com (free sql scripts + SQLDIR parser)
> > Aspeda.com (free Oracle monitoring tool)
>
> Thanks - We have raised a TAR with Oracle, and found a very similar
> call already set. It had not been responded to.

If it's serious enough (production issue your business is suffering, etc.) then page duty manager and rase to P1.

> Did it ever work. Kinda. The jobs are scheduled to repeat. They might
> run 20 or 30 times sucessfully, then they for some reason get stuck in
> this 'started' mode. We have other jobs submitted that run and run
> without problems.

Have you looked at tracing OEM? There's got to be a way to bump up a trace level and check trace files for clues. You need to give them as much as you can. Oracle support is based a lot on their knowledge base (WebIV). Metalink is just a subset of what they have access to. If you don't provide enough information they have to search through too many articles and run you down the wrong path. If you are beginning to feel that this is a new issue then push for opening a new BUG with DEV.

> Monitoring software - what I'd like is something that identified the
> thread under W2K that OEM has kicked off to run that job. At least
> then I could kill the individual thread. Assuming that the jobs are
> indeed started as threads within the ORACLE process.

I wouldn't go that route it just dosn't feel right. You purchased something that supposed to handle failures notifying you automatically. You shouldn't have to bolt-on another APP to handle that.

Regards,
Vitaliy
DBAToolZ.com (free sql scripts + SQLDIR parser) Aspeda.com (free Oracle monitoring tool) Received on Wed Jun 04 2003 - 13:22:48 CDT