Clarity

We are validating v15.2 in a non production environment and have come across an issue with jobs not starting when they should.  The scenario where this happens is:

Job A and Job B are incompatible with each other.

Job A is submitted and starts processing.  While it is processing Job B is submitted. 

While Job A is running Job B has a status of Waiting.

When Job A completes the status on Job B updates to Scheduled but the scheduled time is the time it was originally submitted so it is in the past.  This job doesn't move to processing and just sits at scheduled.

Has anyone else come across this issue?

Is this an upgraded environment  ?

Have you verified what is coming up in the bg logs ?

Regards,

Srikanth G

Hi Srikanth,

This is an upgraded environment.  We have checked the logs and have sent them to CA but nothing is showing up.

Regards,

Marina

Have you tried to remove and recreate bg ?

NJ

I had not tried that but did try it after your suggestion.

This has not resolved the problem.

Regards,

Marina

Hi MarinaFlood, 

I am not sure if this scenario is reproducible for you on every cases that you mentioned in the discussion topic. If this issue happened only once or for some cases then please check if there are orphan instances of JOB B in the database. 

Please compare these 3 tables to see if you can find out any orphan job instances, based on the Job ID: CMN_SCH_JOBS, CMN_SCH_JOB_RUNS and CMN_SCH_JOB_LOGS.

Thanks,

Abhisek Dhar