autosys job does not auto start

[Anon Anon]

hi
I have created autosys job and scheduled to run daily but its not auto start, also tried job control > start job but doesn't start .  the only way it starts is force_startjob. why is it not starting on predefined time

 

thanks

[Mark_Hanson]

Please post the job definition ( autorep -q -J <job_name> ) and job detail report ( autorep -d -J <job_name> )

[Anon Anon]

Hi

 

here is job definition

 

insert_job:
job123.databaase_backup   job_type: CMD

command:
/oracle/backup.ksh 

machine:
db****

owner:
oracle

permission:

date_conditions:
1

days_of_week:
all

start_times:
"18:00"

description:
"'RMAN Backup to tape'"

std_out_file:
"/oracle/log/$AUTO_JOB_NAME.`date -u +%FT%T`.lp2.log"

std_err_file:
"/oracle/log/$AUTO_JOB_NAME.`date -u +%FT%T`.lp2.log"

max_run_alarm:
150

alarm_if_fail:
1

[Chandru.Venkataraman]

Hi -

Please ensure the machine: db**** is NOT in Offline or Missing status (autorep -M <machine_name> -d).

 

Thank you,

Chandru

[mark..williams]

I agree with the earlier posts.

Please make sure the machine is not offline or missing.

autorep -M <machine_name>

 

 

Additionally, as you defined date_conditions you cannot issue a

sendevent -E STARTJOB -J jobname against your job.

You would need to issue the

sendevent -E FORCE_STARTJOB -J jobname

That tells autosys to start the job NOW, regardless if the conditions

have not yet been met.

 

As for if/why it is not running based on the date_conditions, your

planned schedule, we would want to see the results from

autorep -d -J jobname

so we can see if there is a future STARTJOB event listed that

has not yet been processed.  That is what one would normally expect to see.

If there is not one, then re-saving the job definition should generate one.

[Lenn Thompson]

Alex,

 

Good afternoon? How are you making out with your problem? Did the suggestions offered here in the community help? Let us know!

[Legacy User]

Hi

I would suggest to update the job to see the next calculated start time

Then  to confirm, as said previously, get  the output of  'autorep -J -d'

You should see the Job with a STARTJOB event and its next start time with an Event Status " UP"   (for Unprocessed Event)

On that specific day and time, look into the event_demon log. You should see a message telling you why it is not scheduled

 

jil <job.jil

______________________________________________________________________________

CAUAJM_I_50323 Inserting/Updating job: job123.databaase_backup

CAUAJM_I_10122 Job 'job123.databaase_backup' scheduled: 04/22/2016 18:00:00

CAUAJM_I_50205 Database Change WAS Successful!

______________________________________________________________________________

CAUAJM_I_52301 Exit Code = 0

______________________________________________________________________________

 

autorep -J job123.databaase_backup -d

 

Job Name                                                         Last Start           Last End             ST Run/Ntry Pri/Xit

________________________________________________________________ ____________________ ____________________ __ ________ _______

job123.databaase_backup                                          -----                -----                IN 0/0

 

  Status/[Event]  Time                 Ntry ES  ProcessTime           Machine

  --------------  --------------------- --  --  --------------------- ----------------------------------------

  [STARTJOB]      04/22/2016 18:00:00    0  UP

    <Event was scheduled based on job definition.>

 

And finally if everything looks good but the Job does not start, I would suggest to open a case in CA support

 

Thanks and regards

Jean Paul