Kepware Knowledge Base: Solution
What are Table Constraint errors in DataLogger?
Last Update: 11/12/2018
When Store and Forward is enabled, Store and Forward cannot recover records that fail to insert due to table constraint violations.
- Records that fail to insert into the database table due to a table constraint will log to the data store file. All subsequent records will log to the data store file until the table constraint violations are resolved.
- Options for table constraint violation resolution:
- With No Data Loss
- Remove the table constraints from the database table.
- Change the log group to "Create a new Table once and append" to a create and log to a new table. Tables automatically created by DataLogger will not have constraints on data fields.
- With Data Loss
- Disable Store and Forward. DataLogger will no longer attempt to recover records in the data store file. Subsequent records that fail to insert are discarded.
A record in wide data format may contain tags values from different sources. Trigger events generated by tags from one data source may initiate a record insert before data is available from other tag sources. As such, record inserts in wide data format are inherently susceptible to table constraint violations.
©
2022
PTC Inc. All Rights Reserved.