It was recently brought to my attention that in the logs for a driver, SLProtocol was logging a 'ReadColumnData' error. I was wondering if someone could shed some light on what could be causing these logs as it does not seem to be a driver issue. My best guess is that an external source (driver, automation, etc..) is trying to access some information from the table and it failing to retrieve it. Any suggestions on the source of this would be appreciated.
That logging is probably written when your element (re)starts?
This is pointing that the stored data for this table is being read out from the database when the element is starting.
It's finding a stored value for pid 3202 and that is pointing to a primary key e.g. "12898". However when it's reading out the stored primary key column (e.g. pid 3201), it can't find this value "12898" in there, so there is invalid data present in the database and it's not going to load the data of that row for pid 3202.
Root causes could vary how it gets in such situation: adding and removing the same row(s) at a high rate could influence write actions order as different threads are busy, force shutting down a server while the delete action was busy,...