Intermittent outages on FMS with gaps on graphs on many dashboards. The issue is not isolated to a single dashboard or cartridge.
The FMS environment has a large number of old alarms that have not been cleared over a long period of time.
The default alarm purging - part of the nightly DB maintenance - operates on cleared alarms only.
Workaround #1:
Run the following Groovy script to purge all alarms that were created more than 30 days ago:
startDate = new Date(0);
endDate = new Date(System.currentTimeMillis() - (30 * 24 * 60 * 60 * 1000L));
server.AlarmService.purgeAlarms(startDate, endDate);
Workaround #2:
When the alarms table is extremely large - Check size in the FMS support bundle Diagnostic snapshot ( search for "ALARM_ALARM")- and has a huge number of rows ( e.g. in the millions), purging via the script - from workaround #1 - is likely to take a long time. It would be best to truncating the table as this would be much faster; however, this would purge all alarms.
1. Create table ALARM_ALARM_TEMP as select * from ALARM_ALARM where created_time>SYSDATE-30;
2. Truncate table ALARM_ALARM;
3. Insert into ALARM_ALARM select * from ALARM_ALARM_TEMP;
4. Drop table ALARM_ALARM_TEMP;
------------------
When finished, only 30 days worth of alarms will be left.
