Hi Herman,
There are two aspects to this:
- Getting the crontask running again
- Understanding what has gone wrong
Getting the crontask running again
==
Before you take any action please:
export the contents of the TASKSCHEDULER table to Excel - you will need SQL level access to export this
Confirm that the date fields contain the date & time.
keep a copy safe.
That table contains details of all the crontasks that are scheduled and when/where they last ran. It will be useful when you want to understand why the crontask failed.
The first option to try is just stopping the crontask instance and then starting it again.
Entries should appear in the crontask history.
If that doesn't work then it suggests that the JVM running the crontask could be having serious problems.y
In that case you will need to restart the JVM
Understanding what has gone wrong
==
you should look at the SystemOut.log/SystemErr.log file for the time that the crontask should have run.
there are likely to be errors there.
if you aren't sure where those files are then please read my article here:
http://www.linkedin.com/pulse/introduction-most-important-maximo-log-file-mark-robbins
If there are no errors there then it could indicate that the JVM has experienced a serious error e.g. run out of memory and generated a heapdump.
If you get really stuck then reach out to me and I may be able to analyse the logs for clues.
best regards,
Mark