Disabling (or enabling) general job execution in Oracle 10g
disabling and enabling job execution in Oracle DB has two ways:
If you are using dbms_jobs, it’s handy to set
job_queue_processes to zero to disable the execution of jobs,
and set it to a value >0 (maybe 100) to enable.  If you are
using dbms_scheduler, this parameter does not work for you. You
will have to use package functions to disable   or to enable
job execution. Keep the reverse sense of the TRUE/FALSE
parameters in mind (you are deciding whether to DISABLE the
scheduler or not)!  Hope this helps   4 Responses to “Disabling
(or enabling) general job execution in Oracle 10g”    1. Jorn
Hansen Says:      What happens when I enable the dbms_scheduler?
Will all scheduled jobs that have not been activated start
running or will they reschedule using schedule information?
It seems to me, that they will run all at once. I.e. if you have
disabled the scheduler and now enable it, you might experience
that a lot of jobs will run all in one burst