Supression the number of alarms in Oracle probe

Discussion created by JFermenich on Nov 28, 2006
We are running into an issue with the oracle probe and I'm wondering if anyone has some ideas on reducing the number of alarms we get.

When a tablespace is unable to do its next extent, the oracle probe sends an alarm, however it sends the alarm for every single segment of the tablespace. This leads to 10-30 alarms for just one table. Is it possible to build a supression key or something of the sort that will only create one alarm for the event, but still be able to delve the info for the segments affected?

Thanks in advance for your help!