Specifying when a failed job is to retry running

Using Oracle's DBMS_SCHEDULER is there any way to specify when a failed job is to retry running again?  Our scheduled jobs are of the variety that if they fail, we would like to wait an hour before retrying running them again.  The Oracle online documentation on this seems to indicate that a scheduled job fail will be instantly retried to run again (up to max num retries).

              DBMS_SCHEDULER.CREATE_JOB (
                job_name            => strJobName
               ,job_type              => strJobType
               ,job_action          => strJobAction
               ,number_of_arguments => 1
               ,start_date          => dteStart
               ,end_date            => dteEnd
               ,repeat_interval     => 'FREQ=HOURLY;INTERVAL=1'
               ,enabled             => FALSE
               ,auto_drop           => FALSE
               ,comments            => strComments
              );
             
              DBMS_SCHEDULER.set_attribute (
                name        => strJobName
               ,attribute   => 'max_failures'
               ,value       =>  numMaxRetryAttempts
              );
crayola3Asked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

DavidSenior Oracle Database AdministratorCommented:
I have to concur that the restart cannot be deferred -- except in the following condition:

If restartable is set to FALSE for the job:
If the job is a run-once job and auto_drop is set to TRUE, the job run is done and the job is dropped.
If the job is a run-once job and auto_drop is set to FALSE, the job is disabled and the job state is set to 'STOPPED'.
If the job is a repeating job, the Scheduler schedules the next job run and the job state is set to 'SCHEDULED'.
 
DavidSenior Oracle Database AdministratorCommented:
crayola3Author Commented:
Confirms what I had thought about how retry works for dbms_scheduler.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Naveen KumarProduction Manager / Application Support ManagerCommented:
in simple terms, there is no answer as of now for your requirement with 10g dbms_scheduler. I mean dbms_scheduler does not have an option for your requirement as far as i am aware. I wish to some option/solution to your requirement in oracle 11g version.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Oracle Database

From novice to tech pro — start learning today.