Store and Forward Quarantined item- Duplicate Primary Key Error in Tag Historian

Ignition
1

We are facing intermittent primary key violation error in ignition Tag Historian while storing data to SQL server.

Error observed: violation of primary key constraint cannot insert duplicate key.

Forword setting:

write size:25

write time:1sec

disk cache: Enabled

observed behaviour-

data already present in database with tagid and timestamp. however, store and Forword retries the same records again.

one more thing if batch size/write size 25 and if any records in batch fail will entire batch is retired or pending record only retired?

Appreciated any help.

2

Im working with ignition support on the exact same issue. What SQL server are you using ?

3

Hi, I am using Microsoft sql server 2016 SP1 (13.0), Express Edition.

4

Which version of Ignition is this happening in and is it only a specific type of tag?
In 8.3, we have a known issue where memory tags on startup are getting a duplicate history record processed because we are persisting the timestamp when it last changed after a restart now.

5

version is 8.1.26 and it’s not for specific tag random tag every time and tags are OPC tags.

6

I would recommend reaching out to to support regarding the issue you are seeing. In looking at what has been fixed since the release you are currently using, there is 1 bug that could be related:

Fixed in 8.1.27: Fixed issue where duplicate timestamps would be created when OPC quality changes.

7

@rahulsatpute5996 ive made some progress on this with the help of the support team. what we have found so far is that on postgres if there is a single violation in a batch insert then the entire batch is quarantined. If anyone else is using Postgres you can add these connection settings to prevent it:

reWriteBatchedInserts=true;autosave=always;cleanupSavepoints=true

Still getting some real violations even with these settings but only the real violations are being quarantined.