This content has been marked as final. Show 2 replies
Thanks for your response Gaurav. Reviewed the pointed out metalink note id's and they were very helpful.
The NEXT_SCHEDULED_CHECK in alr_periodic_alerts_view is set to 'T' for these two alerts which means it will be picked up by the next Periodic Scheduler run and hence it picked up. That clarifies the issue.
But this behavior was experienced only after the recent change, and with the past changes to these alerts, it used to get fired only on the scheduled date(like 12th in this case) and even at that times the NEXT_SCHEDULED_CHECK was set to 'T'.
The only extra modification this time was CHECK_START_TIME which was changed from 48600 to 0.
I was able to investigate further on this and when I set this back to 48600 and take date_last_checked back in time for this alert, it was not getting fired/run in the next time. Its running on the scheduled date only.
Appreciate any explanation on this ?