Job scheduling stops abruptly shortly after restart

Document ID : KB000118045
Last Modified Date : 24/10/2018
Show Technical Document Details
Job scheduling abruptly stops shortly after a restart to Applications Manager. Further investigation show that scheduling is only successful for the first run of the Job. All Ad-hoc requests are successful.

After the first run is complete, the next run date is evaluated but ignored. This behavior is repeated once more if Applications Manager is restarted again.
This erroneous behavior can be due to invalid data in the AW_MODULE_SCHED table, generally caused by an update made from outside the Java Web Client.

Review for any database updates to the AW_MODULE_SCHED table or any other Table not made through the Java Web Client such as:
  • External API
  • Toad
  • Sql Developer
  • Sqlplus
  • Any tool that connects and makes updates to the Applications Manager's database
Revert any changes found and restart Applications Manager.