Issue
The database is logging multiple alarm entries each time a point goes into alarm.
Product Line
Andover Continuum
Environment
- Alarms
- MSMQ
- SQL Server
- Event Notifications
Cause
Various causes.
Resolution
The following is a list of conditions which may produce multiple alarm event logging.
Network Latency In cases where the network is extremely slow or workstation are overburdened, the process of logging alarms may be slowed to the point where a second alarm is sent by the controller while the previous alarm is still in the process of being logged. In one particular case the logging workstations associated with the duplicate log entries were all in India while the database server was in the US. The problem was resolved by changing the ACCID of all of the India workstations to 253 or higher so that they were not involved in logging alarms.
Database insertion errors If there are database insertion errors in the ACCTrace, Cyberstation cannot send an acknowledgement that the alarm event has been logged. Consequently the controller will continue to send the alarm event until it receives notification that the alarm has been successfully logged.
Database Server latency It is not unusual to see Database Insertion errors when a Continuum DB server is struggling to keep up with the demands that the system has placed on it. A use Task Manager and other tools to evaluate the processor and memory consumption.
Enhanced Alarm Logging and Enhanced Alarm Delivery. If Enhanced alarm logging/delivery is broken due not shutting down all workstations before doing a database update, it is possible to have combination of enhanced and old style alarm delivery. The solution is to shut down all workstations and perform a db update with Enhanced Logging and Enhanced Delivery selected.
Workstation Resources. If the logging workstation is over burdened with reports, programs, extended log downloading, etc.
