April 3rd, 2008

Disabling (or enabling) general job execution in Oracle 10g

Hi,

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

dbms_scheduler.set_scheduler_attribute('SCHEDULER_DISABLED','TRUE');

or to enable

dbms_scheduler.set_scheduler_attribute('SCHEDULER_DISABLED','FALSE');

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
Usn


By usn in Oracle 



You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.

2 Responses to “Disabling (or enabling) general job execution in Oracle 10g”

  1. Jorn Hansen Says:
    February 2nd, 2009 at 2:30 pm

    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.

  2. usn Says:
    February 2nd, 2009 at 4:42 pm

    Yes, they will run in one burst. That’s exactly what happens if you stop the database for some time and restart it: All missed jobs will start.

    Usn

Leave a Reply