I have a very strange issue. I have 4144 tags that are being logged to history that don’t exist in the tag browser, but that have recent (as in to now) history being logged for them, and they’re not just 0’s or null data, they’re moving as if live. In total, they’re logging about 324MB per day (or 115GB per year) so it’s not insignificant!
Not too long ago I noticed many udt instances that were invalid. I have no idea how they got there, and when I say invalid, I mean their instance name didn’t match their parameter configuration. My guess is that they were created by copying and pasting existing UDT instances and subsequently losing the new instances - which is incredibly easy to do, as pasted tags aren’t automatically selected, hence if you have 500 UDT instances called T1000-T2000 (often discontiguous), then you’re bound to lose the pasted UDT instance as you have no idea what the next available number is that it’ll use to rename it.
I identified these and bulk deleted them, but it would appear that they are still happily logging away in the background to history.
From the looks of it, most of these tags have nulls for both the
fingerprint in the
sqlth_te table columns, the curious detail being the fingerprint being null…
This seems like a bug to me.
What is the best way to resolve this? Should I just retire the tags in the