I am running an Oracle v2 SQL Sensor on a remote probe, and am also running the same SQL in an Oracle Depracated SQL sensor. The V2 sensor will intermittantly return "No Data", whereas the V1 sensor does not.
The SQL is a query that will never return a null result, as below -
select (cast(sys_extract_utc(systimestamp) AS DATE) - cast(max(eventtimecolumn) AS DATE)) * 24 * 60 * 60 from eventtable
We use this to check the number of minutes difference between the current UTC time & the max UTC time of a column in a (small) table.
As the V1 sensor is OK, but the V2 sensor returns "No Data" - is there a problem with the V2 sensor ?
Article Comments
Hello Dave,
thank you for your post.
- Please confirm, the SQL v2 sensor is intermittent?
We'll need to confirm the exact version of PRTG that you're running, additionally, we'll need you to enable the " Write sensor result to disk (Filename: "Result of Sensor [ID].txt")" option from the sensor and share the result (which will be stored under C:\ProgramData\Paessler\PRTG Network Monitor\Logs (Sensors)\ on the probe on which the sensor was deployed.)
Ideally we suggest that you open a Support ticket so that you may share a support bundle and the other required logs, which can't be easily attached here.
Best Regards,
Apr, 2016 - Permalink
Hello Dave,
thank you for your post.
We'll need to confirm the exact version of PRTG that you're running, additionally, we'll need you to enable the " Write sensor result to disk (Filename: "Result of Sensor [ID].txt")" option from the sensor and share the result (which will be stored under C:\ProgramData\Paessler\PRTG Network Monitor\Logs (Sensors)\ on the probe on which the sensor was deployed.)
Ideally we suggest that you open a Support ticket so that you may share a support bundle and the other required logs, which can't be easily attached here.
Best Regards,
Apr, 2016 - Permalink