Transaction group quit writing to DB Please help!

Hi
I guess I'll try a different title. I had a transaction group set up that read from a PLC tag and saved that to my DB. This was working, and I have 605 rows of data collected in the DB. For some reason, it just stopped. The transaction group status shows that it is executing, that it is triggering, that it is in fact writing to the DB, but no new data is ACTUALLY in the DB. Rows stay at 605.
Does anyone have any idea what could have happened, or how to fix it?

Thanks!

Don't post the same thing twice.

If anything, bump your old topic next time. This time I'll close it for you.

If you need an immediate response call support.

Sorry about that, thought I may not have explained myself well.

To my knowledge, Transaction Groups execute on the gateway and not the client. Have you checked the gateway logs to see if any errors are thrown there?

There is also an 'Events' tab next to the 'Status' tab at the bottom of the Transaction Groups window ('Status' is where I believe you're finding the info about executions, triggers, writes, etc.). It might be worth checking the 'Events' tab for clues as well, if you haven't yet.

While there was nothing in either the status or events tabs, looking in the gateway logs revealed the problem:

java.lang.RuntimeException: java.sql.BatchUpdateException: Operand type clash: datetime2 is incompatible with int

I had changed an opc item at one point to have a datetime data type (trying to get it to show up in a table as 2023 instead of 2,023) and never noticed the data wasn't updating after due to no errors showing in the status tab. Changed it back to int4 and the data is now being stored in the DB again. Thanks!

1 Like

There's an edit pencil under each of your posts. You can improve them there (although if someone has already answered your post as originally written then make it clear that you're adding information).