Re: DBMS_JOB fails to schedule job

From: Richard G Ramirez <ramirez_at_iastate.edu>
Date: 1995/11/07
Message-ID: <47odij$kj4_at_news.iastate.edu>#1/1


Vikram:

Thanks for the information on DBMS.JOB. We tried it and it is working now.

I want to capture usage statistics at the end of the day to keep track. Our company is only now putting applications into production. The statistics will give us some idea of what is going on.

We initially created 5 job queue processes. We then reduced it to one and assumed that it will run several jobs. Is this true?

Each queue comsumed close to 3 CPU minutes per hour just to check. Someone said that this is too much and that we should use Unix's cron instead. I like having everything in one environment. Any ideas?

John Wireman says hi. I showed him your message and he remembered you.

Sorry to answer this way. I am new here and my e-mail does not work yet.

Richard
--

Richard G. Ramirez

Richard,

Your code looks fine, however check if the following parameters are set in the init<sid>.ora file. You can check the current values by executing a show parameters in sqldba. The parameters are :

JOB_QUEUE_INTERVAL = a value in seconds for the process to wake up and see if it

                      has to do anything , 0 to 60 mts.

JOB_QUEUE_KEEP_CONNECTIONS = FALSE/TRUE based upon your needs.

JOB_QUEUE_PROCESSES = Default is 0 meaning no background processes. You have to

                       at lease one process for jobs to be executed.


Edit the file dbmsjob.sql in the $ORACLE_HOME/rdbms/admin directory ( this is for most unix systems), for a through discussion on this.

--

Richard G. Ramirez, Ph. D.
Assistant Professor of MIS
Iowa State University Received on Tue Nov 07 1995 - 00:00:00 CET

Original text of this message