Re: Jobs submitted under OEM start but do not finish

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>...
> > We are trying to track down the source of a problem and would
> > appreciate any pointers on where to start looking.
> >
> > Oracle 9i ( 9.2.0.1.0 ) runing on Windows 2000 Advanced Server.
> > Compaq Hardware, 2GB RAM, SANS disk storage.
> >
> > We have a number of jobs that have been started are still showing as
> > "started" through OEM long after they should have finished. These are
> > jobs that should only take seconds to run, but are still not finished
> > after several days.
> >
> > Q2. Are there any other tools that could be used to monitor the
> > progress and state of any submitted jobs to see why they might have
> > stalled?
>
> You are asking for monitoring software to monitor ...
> monitoring software.
>
> 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.

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.

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.

One thing I cam across was that OEM was creating files in the C:\temp directory. I'm asking the DBA to change this to a directory of our choice. Looks like a registry change to make it happen. Received on Wed Jun 04 2003 - 04:53:06 CDT