<![CDATA[Trouble with ODBC SQL Polling]]>Hello Victor,

I've managed to build and launch ODBC subagent tried it and got some issues. Current query returns right result, but those results stored previously die or something wrong happens to them. I have included the printscreens of management console showing this and screen of collection configuration.

Agent is configured with the following lines:
*ODBC
Query = SQL.MySQLQuery:mybase:SELECT COUNT(*) FROM USERS WHERE USERACTIVE = 1 AND USERDELETED = 0:60

Normally query should return 171 or something like this.

err4.PNG

err1.PNG

err2.PNG

err3.PNG

]]>https://forum.netxms.org/topic/1851/trouble-with-odbc-sql-pollingRSS for NodeFri, 13 Nov 2026 16:08:13 GMTTue, 31 Jul 2012 09:53:35 GMT60<![CDATA[Reply to Trouble with ODBC SQL Polling on Wed, 01 Aug 2012 09:11:35 GMT]]>Hello Victor,

I have added SNMP string polling and it has the same effect as ODBC polling. Current polled value is good and stored are ruined.

Best regards,
Roman

]]>https://forum.netxms.org/post/8081https://forum.netxms.org/post/8081Wed, 01 Aug 2012 09:11:35 GMT<![CDATA[Reply to Trouble with ODBC SQL Polling on Tue, 31 Jul 2012 12:19:19 GMT]]>As all previously stored values displayed correctly now, that means a bug on client side - either in client library or in management console itself. Can you check any other string DCIs if you have any?

Best regards,
Victor

]]>https://forum.netxms.org/post/8070https://forum.netxms.org/post/8070Tue, 31 Jul 2012 12:19:19 GMT<![CDATA[Reply to Trouble with ODBC SQL Polling on Tue, 31 Jul 2012 11:49:41 GMT]]>Hello Victor,

Changing type to integer effectively solved the problem. All previously stored values are now displaying correctly. The one thing I don't understand is why did this happen?

]]>https://forum.netxms.org/post/8067https://forum.netxms.org/post/8067Tue, 31 Jul 2012 11:49:41 GMT<![CDATA[Reply to Trouble with ODBC SQL Polling on Tue, 31 Jul 2012 10:31:32 GMT]]>Hi!

It looks like problem on server or in management console, because history is corrupted. Last value always good, which means that agent reports correct value. Can you try to change data type of this DCI to integer? Also, is there any other DCIs which experience same problem?

Best regards,
Victor

]]>https://forum.netxms.org/post/8065https://forum.netxms.org/post/8065Tue, 31 Jul 2012 10:31:32 GMT