7–4
N
OTIFICATIONS
(A
LERTS
AND
E
VENTS
)
The appdb typically includes four (4) special tables that are not archives (sourced from a log, but instead hold data from received from the alarm subsystem
As shown in Figure 7-3
, these tables almost always appear in the appdb, alert tables at the top (archives in the middle, then event tables at the bottom.
Figure 7-3
ALERT and EVENT tables are not archives, but store details on alarming.
The names of these tables in the appdb areas follows:
ALERT.ALERTHISTORY
—Stores all occurrences of alerts (runtime or COS) from binary objects and multi-state object, plus each alert acknowledgment (the time and user).
ALERT.UNACKEDALERTS
—Stores only alerts not yet acknowledged by any system user.
EVENT.EVENTHISTORY
—Stores all event occurrences (alarms, such as application alarms (alarm low, alarm high, fault, etc) and system alarms (device up or down, station up or down, etc, plus each alarm acknowledgment (the time and user).
Share with your friends: |
