Job Scheduled did not ran

[karunakar.ds]

Hi,

As one of the JobSequence got scheduled at 11.30 PM yesterday from Director and did not ran. We did not get this issue earlier as this job used to run daily.

Below is the only one entry found in the job log.

DS.SCHED: Started at: 23:30:01 14 DEC 2009, directory MID_PROD
JobNumber=835, TraceLevel=0/50/1/0/0, JobInstance=1

Did anybody come across this issue earlier and please let me know if you found any resolution to this issue.

Thanks,
KK

[Sainath.Srinivasan]

How did you conclude that the job did not run ?

What was changed between your last successful schedule and this one ?

Was the user given for schedule job different now ?

[karunakar.ds]

Hi Sai,

Since this job is not triggered, I ran this job manually. Also the job status for this job is showing of previous run.

I can see only below unformation in the job log.

DS.SCHED: Started at: 23:30:01 14 DEC 2009, directory MID_PROD
JobNumber=835, TraceLevel=0/50/1/0/0, JobInstance=1

I verified the Crontab and did see that the job schedule is intact.


Thanks,
Karunakar

[chulett]

I've seen that myself years ago but Ascential support could never pin down a cause and it "went away" on its own. Perhaps by now they might have a clue.

[Sreenivasulu]

I get this problem with 'windows scheduled tasks' but never came across on scheduling with 'datastage'. In fact i suggest to users to go for 'crontab'
instead of 'windows scheduled tasks'

Regards
Sreeni

[chulett]

Mine was with UNIX server, so cron scheduled via Director.

[Abhijeet1980]

No respite unless you successfully emulate the problem in front of support from IBM.

Rare and hence arguable.

Many regards,