Secondtimer table

The Secondtimer table is a transient table. The system creates and deletes records in the table as required by applications. Unlike timer records, Secondtimer records are replicated to all systems for seamless functionality after a mode switch.

The following features use Secondtimer records:

• Command timeout processing

• Timed Alarm Inhibit

Since command timeouts are configured in seconds, they use short-lived Secondtimer records. The number of Secondtimer records created depends upon the number of commands that the system currently executes at any one time.

With Timed Alarm Inhibit, however, you can configure the system to inhibit alarms for a number of days, hours, and/or minutes. This functionality gives rise to long-lived Secondtimer records. Since they are long-lived, it is important to size the system appropriately for the number of analog, status, rate, multistate, rtstring, connection, remote, tank, and flowTotalConfig records that you may inhibit concurrently. Since the time at which you inhibit these different records will vary, there will be numerous overlapping Secondtimer records.

The default number of Secondtimer records upon installation is 25,000. AVEVA does not recommend decreasing the size of the table.

For information on using SchemaConverter to alter table sizes, see Extend and modify the database structure.

For more information on command timeout processing, refer to "Timeout Alarms" in volume 1 of the RealTime Administrator documentation.

For more information on Timed Alarm Inhibit, refer to "Timed Alarm Inhibit" in volume 1 of the AVEVA Enterprise SCADA RealTime Administrator documentation.