About suspended job

Nicolas Gasparotto

Hello,

I'm working on OEM 12.1.0.1 on AIX5.3 and Oracle 11.2.0.3.

If I suspend a job execution, I expect any of the coming executions not being fired until resume. However, they are triggered (but not executed) falling in "problem" status stating "skipping" on each target of the job.
It is wrong IMO, well, at least under OEM 11gR1, the suspended job were not triggered at all.
Here, I have several hundreds jobs having "problem", but very tedious now to distinguish which ones are expecting problem (from suspended job) from the ones which have really a problem. Note that if I resume the job, whether the job is scheduled as expected on the next run, the problem still remains.
Any clue on how to overcome this issue ?
Thanks,

Nicolas.

Adeesh Fulay

Nicolas,

We have an ER to move skipped to its own status bucket, and not overload the problems bucket. This should be available in a future release. Unfortunately, for now there is no way to identify unless you drill into the job details.

Adeesh Fulay

Nicolas,

We have an ER to move skipped to its own status bucket, and not overload the problems bucket. This should be available in a future release. Unfortunately, for now there is no way to identify unless you drill into the job details.

Nicolas Gasparotto

Thanks for the info, I'll wait for a future release then.

Nicolas.

Jvishen-Oracle

The Job activity page has filters which will allow you to find the suspended job. If you look at the "Status" drop down, the text "Suspended" is listed under "Active" and "skipped" is listed under "Problem" status. If you select "Suspended" you should be able to locate the suspended job easily.