1
153102
Guest
In our OEM standard installation, I have several schedules applied to a database over the course of a day - regular hours, backup period and 2 overnight periods (because schedules cannot cross midnight). An alert on busy DB activities was thrown at the end of one of the schedules. It was a fairly brief spike, however the alert clear did not come until the beginning of the same schedule the next day. Once a "watch" ends monitoring goes on to the next one and the two do not communicate. Just by following OEM alerts one would think I had this spike for nearly 20 hours. Support confirmed this was expected behavior (case 00366673) and suggested posting this idea. I suggest when an alert or at least some alerts (that might be pertinent) are in progress at the end of a schedule they are watched for a period of time after the end of the schedule. If the same alert and configuration exist in the next schedule, it could just take over the alert itself. Or schedules might be allowed to overlap some. Thank you
Continue reading...
Continue reading...