<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Issues with DCI's,transforms, and SQL errors.]]></title><description><![CDATA[<p dir="auto">I have a new 5.2.4 install, and I was just trying to get some of the initial stuff set up.  I was building some dashboards, and one of the DCI's polling from SNMP was giving me a value that needed to be /10  (It's a voltage, and the data polled from SNMP is like 578, when the voltage should be 57.8).    So, I go to the template to add the transform, and I cant get it to work (even though the test works fine).  I mess with it for a while, and then by chance I notice in the logs that there is an error every time I "start data recalculation" on the node's DCI.    I'm not 100% sure what I'm reading, but it seems that there is a column missing. </p>
<p dir="auto">Database query failed (Query: SELECT date_part(\u0027epoch\u0027,idata_timestamp)::int,raw_value FROM idata_sc_30 WHERE node_id\u003d245 AND item_id\u003d1094 ORDER BY idata_timestamp; Error: 42703 ERROR: column \"node_id\" does not exist\nLINE 1: ..._timestamp)::int,raw_value FROM idata_sc_30 WHERE node_id\u003d24...\n ^)"</p>
<p dir="auto">I figured it was something that I was doing, but then I also noticed that 5.2.3 listed "#140 (SQL errors after converting database to TimescaleDB)" ...and this was installed as a TimescaleDB...  So, I'm thinking that maybe this is jut another, or unfixed bug in 5.2.4.   It was a new install of 5.2.4 though, so no conversions, or upgrades. </p>
<p dir="auto">Not sure if anyone can confirm, or point me in the right direction? </p>
<p dir="auto">EDIT:  I forgot to mention, that nxdbmgr check passes with no errors. </p>
<p dir="auto">Thanks!</p>
]]></description><link>https://forum.netxms.org/topic/8219/issues-with-dci-s-transforms-and-sql-errors.</link><generator>RSS for Node</generator><lastBuildDate>Fri, 13 Nov 2026 11:48:26 GMT</lastBuildDate><atom:link href="https://forum.netxms.org/topic/8219.rss" rel="self" type="application/rss+xml"/><pubDate>Tue, 29 Jul 2025 05:35:34 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Issues with DCI's,transforms, and SQL errors. on Tue, 29 Jul 2025 18:10:55 GMT]]></title><description><![CDATA[<p dir="auto">Thank you Filipp!   </p>
<p dir="auto">I believe your assessment is correct; eventually, I noticed (later that night) that the transform was working correctly.  Since I was forcing the recalculation, getting the error, and noting that the value wasn't changing, I thought it was broken entirely.  </p>
<p dir="auto">I've cleared the historic data, and now the data/graph is displaying correctly.  </p>
<p dir="auto">Appreciate the help and fast response as always!</p>
]]></description><link>https://forum.netxms.org/post/34640</link><guid isPermaLink="true">https://forum.netxms.org/post/34640</guid><dc:creator><![CDATA[cbwecomm]]></dc:creator><pubDate>Tue, 29 Jul 2025 18:10:55 GMT</pubDate></item><item><title><![CDATA[Reply to Issues with DCI's,transforms, and SQL errors. on Tue, 29 Jul 2025 11:10:44 GMT]]></title><description><![CDATA[<p dir="auto">#140 is relate to new nxdbmgr functionality - it now can do in-place conversion of Postgres DB to Timescale. </p>
<p dir="auto">But this here is a different bug - I've created a ticket for it: <a href="https://track.radensolutions.com/issue/NX-2819" rel="nofollow ugc">https://track.radensolutions.com/issue/NX-2819</a><br />
This issue affects only recalculation of historic values, but new values should be transformed correctly.</p>
]]></description><link>https://forum.netxms.org/post/34638</link><guid isPermaLink="true">https://forum.netxms.org/post/34638</guid><dc:creator><![CDATA[Filipp Sudanov]]></dc:creator><pubDate>Tue, 29 Jul 2025 11:10:44 GMT</pubDate></item></channel></rss>