So I was testing out the Oracle tablespace sensor and it created sensors for my tablespaces without any issues. The only problem I can see is the individual sensors don't seem to be reporting their values correctly. For example I have a tablespace flagged as Down - free space below the error limit of 5% so when I look at it I see these results in PRTG:

Free Blocks-396,288
Free Blocks %is empty
Free Space3096 MByte
Free Space %is empty

Using a SQL query I see these values for the same tablespace: 

Total Tablespace size 3096 MBytes
Total Used space 0 Mbytes
% Used 0%

So I'm curious as to why it would report down with less than 5% remaining when in fact the tablespace is empty and has 100% remaining. In looking at the data PRTG is showing 4 tablespaces as having less than 5% remaining but those 4 are fine on space. The only common issue I see is that the 4 tablespaces are not set to autoextend but have distinctly allocated sizes. For those 4 tablespaces the Free Blocks % and Free Space % fields are empty (not calculated).

Article Comments

Hello mcoleman,
we appreciate your contact and report.

  • Kindly confirm, which version of PRTG and which version of Oracle are you running?
  • Please add the Oracle Tablespace Sensor anew, are the results the same?

Best Regards,


Dec, 2015 - Permalink

Sure - PRTG version 15.4.20.4776. Oracle version is 11.2.3.0. I removed and re-added the Oracle Tablespace sensor and it had the same results. The same 4 tablespaces show as below 5% when in fact they are empty.

I also tested against a different database. All the tablespaces that had datafiles that were not set to autoextend didn't calculate free space correctly and reported down (< 5% remaining).

I selected one tablespace that with a single datafile that was set to autoextend no and was showing down in PRTG with no free space calculations. I set the datafile to autoextend yes and PRTG started calculating the free space correctly.


Dec, 2015 - Permalink

Thank you for your testing/troubleshooting.

I will forward these findings to the Sensor's developer, if we're able to resolve the issue it should be fixed in the following Stable releases of PRTG. You can keep an eye on the release notes for any updates/changes.

In the meantime if you're able to query the tablespace sizes using an SQL Expression, please use the Oracle SQL v2 Sensor to display the appropriate values within PRTG.

Best Regards,


Dec, 2015 - Permalink

This bug is probably already fixed in the latest versions. 

November 30th 2015 - Version 15.4.21.5161/5162

Bugfixes [Sensors]:

[...]

Oracle Tablespace sensor now handles auto-extensible files properly.

Jan, 2016 - Permalink