This section describes the settings which have been deprecated from the Gateway schema.
This setting has been deprecated. Please use hours recurrence pattern.
This setting has been deprecated. Please use days recurrence pattern.
This setting has been deprecated. Please use weeks recurrence pattern.
This setting has been deprecated. Please use months recurrence pattern.
The command Database > Suspend (available on Gateway in the Gateways view in Active Console) where you had to tick/untick the "Suspend database" checkbox to suspend /unsuspend logging of database item values has been deprecated.
You should now use the commands DatabaseLogging > Itemvalues > DiscardandDatabaseLogging > Itemvalues > Log. The old command can still be scheduled through scheduled commands / tasks for backward compatibility.
This setting has been deprecated and you should now use discardItemValuesOnError setting.
In this setting, you can configure multiple error codes. When any of these error codes are returned from the database, it triggers discarding of database item values and these updates are not be logged to the database (or saved to disk if the database isn't available).
This setting takes a text input and a wildcard search (pattern) is used to match the error against the error string returned from the database.
For example, the database may throw back error like:
 Can't connect to MySQL server on 'ITRSPC000.ldn.itrs' (110)
Any substring of this error message such as
2003" or "
" or "
Can't connect to MySQL server on 'ITRSPC000.ldn.itrs'" will match
this error message.
To start logging of database item values again, you need to issue command DatabaseLogging > Itemvalues > Log.
Please refer Database logging errors for a list of possible error codes returned from different database vendors.