We had an issue previously due to a bug with scheduler windows not changing
if job_queue_processes was set to 0 at the time the change was scheduled.
DB resource manager also played a part in this.
The bug we believe we hit was 22071881, FYI. There are a few patches out
for it.
Don.
On Thu, Apr 6, 2017 at 12:23 PM, Bill Ndolo <wndolo@xxxxxxxxx> wrote:
If you have oracle tools like sql developer or TOAD configured, you can
easily see where the job is broken.
And yes, share logs.
On Thu, Apr 6, 2017 at 12:11 PM, Kellyn Pot'Vin-Gorman <
dbakevlar@xxxxxxxxx> wrote:
What does the log say at the time of the failure?
On Thu, Apr 6, 2017 at 10:10 AM Terrian, Thomas J CTR DLA INFO OPERATIONS
(US) <Tom.Terrian.ctr@xxxxxxx> wrote:
My scheduler jobs stopped running a month ago:
SQL> select JOB_NAME, NEXT_RUN_DATE from dba_scheduler_jobs where
rownum = 1;
JOB_NAME
------------------------------
NEXT_RUN_DATE
------------------------------------------------------------
---------------
PURGE_LOG
10-MAR-17 03.00.00.100000 AM PST8PDT
Any idea why?
SQL> sho parameter job
NAME TYPE VALUE
------------------------------------ -----------
------------------------------
job_queue_processes integer 1000
--
//www.freelists.org/webpage/oracle-l
--
[image: Kellyn Pot'Vin on about.me]
Kellyn Pot'Vin-Gorman
about.me/dbakevlar
<http://about.me/dbakevlar>
