Hello,
We have a large numer (30+) of Oracle SQL v2 Beta sensors. Most of them perform very well. A few of the queries against the target database are quite complex and take a few seconds to return a result. It appears that if this is longer than about 5 seconds, the sensor throws a "Timeout (code: PE018)" error.
It is quite normal for some of these queries to take a long time to return a result (5 or even 10 seconds), so we need some way of extending the timeout on these particular sensors.
I have noticed that the Oracle SQL sensor (not the v2 Beta version) as well as the Custom ssh / exe / script sensors all have a timeout setting which can be increased: if the script takes longer than this to return a result, then return an error.
However there appears to be no such setting for Oracle SQL v2 Beta sensors. Is there any way that I can change this timeout setting "behind the scenes" maybe?
I guess another way would be to run the SQL via Powershell and add a custom Powershell sensor instead, but I'd rather find an easier way.
Any information greatly appreciated
Many thanks in advance
Tom
Article Comments
Did this more lenient timeout make it into this update? I am still seeing the same issue.
Jun, 2015 - Permalink
Some parts of the changes are part of the "18" branch. Please contact support@paessler.com (you can mention me) for special version of the sensor to see if that fixes the issue.
Jun, 2015 - Permalink
Hi,
Yes, I am still on version 15.2.17.2636 so not yet able to make any changes.
However I have in the meantime moved a couple of particularly slow queries to use the Oracle SQL sensor (not v2 Beta) as this has a timeout setting. This has temporarily resolved the issue for us, but we will try with the new sensor settings when they are available
I am in no rush at the moment and our monitoring is stable so happy to wait for the changes in the stable release
Tom
Jun, 2015 - Permalink
I do have the same problem on the Oracle Tablespace Beta. Currently running on Version 16.1.22.2012 successfully installed.
Is there a new and better version of this sensor available?
Mar, 2016 - Permalink
Dear jlieben
Which timeout did you set in the device settings? (Section "Credentials for Database Management Systems")
Mar, 2016 - Permalink
We tried different time out from 1 minute to 5 minutes. Also the interval has been changed from 1 minute to 5 and even 30 minutes. All with same result. Strange thing is that the problem happens for only a small percentage of the sensors (we have 2400+ oracle tablespaces).
Apr, 2016 - Permalink
Hi,
This is going to become a bigger problem now that you are retiring the Oracle SQL sensor. We have between 5 and 10 sensors using the "old" Oracle type SQL sensor because the queries take over 5 seconds and this sensor has a timeout setting which is configurable.
Oracle v2 SQL sensor still has no such configuration available, so once we upgrade, some of our sensors will fail. Please can you advise if a timeout setting is going to be made available in the Oracle v2 SQL sensor, as this will dictate whether we upgrade or not.
Many thanks, Tom
Apr, 2016 - Permalink
Dear Tom, dear jlieben
The SQL v2 sensor timeout is set by the device setting, "Credentials for Database Management System". The sensor developer just checked it. Are you using the latest PRTG version? How long does the query take to get you a timeout error, is it still estimated to be just over five seconds?
Apr, 2016 - Permalink
Hi Arne,
Thanks for your response. I may be mistaken, but I think the "Timeout" setting in the "Credentials for Database Management System" section is a login timeout, i.e. how long will the sensor try to log in to the database before an error is reported.
What we need (and what is available in the "old" Oracle SQL sensor), is a timeout setting for the SQL execution itself.
When we first tried to use the Oracle SQL v2 sensor, SQL statements taking longer than 5 seconds to execute would be reported in error by PRTG, even though the SQL would complete OK (see original post to this thread). Now that Paessler are retiring the Oracle SQL sensor, we need to be confident that we can migrate SQL queries to v2 which take longer.
Having said all this, it does appear to be more lenient (we havent had any timeouts yet, and we are beginning to migrate sensors from Oracle SQL to Oracle SQL v2), so maybe this has been fixed?
Thanks, Tom
Apr, 2016 - Permalink
Dear Tom
The command timeout should also be set by this field. If you experience timeouts with the v2 sensor, please let me know.
Apr, 2016 - Permalink
By changing the sensor check interval, is it possible to resolve this "Timeout (PE018)" alert?
Feb, 2021 - Permalink
Hello,
the PE018 error is a quite generic error, that an executable (this sensor uses an executable. SQLv2.exe) did not return a result in time. Normally this is caused by long execution times.
Please go to your PRTG installation directory and open the "Sensor System" subfolder. (Usually "C:\Program Files (x86)\PRTG Network Monitor\Sensor System")
Now start the SQLv2.exe and a window will show that offers the same settings as the sensor. It is less comfortable and does not do any checks on the values you enter. Enter your server information and the SQL query.
You you get the expected result table in reasonable time?
Feb, 2021 - Permalink
Dear twills
We will offer a more lenient timeout handling in a future version of PRTG. The upcoming PRTG 15.2.17 will contain some improvements. Please update when it is public, which could be next week.
Jun, 2015 - Permalink