Hi,

we have Version 16.3.24.4980 of PRTG (we cannot upgrade right now because one Server is 2003 in the network with monitored scheduled tasks) and i tested the oracle-tablespace sensor in beta status. Which works fine exept the free space is on every tablespace almost the same. (this cannot be correct bcs it shows us around 32GB Space on every tablespace which is wrong!)

To compare the values we have a oracle Database 11g and our Server contractor gave us a query which sums up different values of tablespace together, to see the same stuff like free space, used MB, Total MB. I've tested it with one tablespace to be sure.

Unfortunatly we get always: "Die angebende Umwandlung ist ungültig"

the query looks like this:

SELECT a.tablespace_name tablespace, ROUND(SUM(a.total1)/1024/1024, 1) "Total Mb", ROUND(SUM(a.total1)/1024/1024, 1)-ROUND(SUM(a.sum1)/1024/1024, 1) "Used Mb", ROUND(SUM(a.sum1)/1024/1024, 1) "Free Mb", ROUND(SUM(a.sum1)/1024/1024,1)*100/ROUND(SUM(a.total1)/1024/1024,1) "Free %", ROUND(SUM(a.maxb)/1024/1024, 1) "Largest Segment Size Mb" FROM (SELECT tablespace_name, 0 total1, SUM(bytes) sum1, MAX(bytes) maxb, COUNT(bytes) cnt FROM dba_free_space GROUP BY tablespace_name UNION SELECT tablespace_name, SUM(bytes) total1, 0, 0, 0 FROM dba_data_files GROUP BY tablespace_name) a where tablespace_name= 'COMPANYNAME_DATA_INDEX' GROUP BY a.tablespace_name;


Article Comments

Hi there,

Please execute the query within your SQL-DBMS and forward us the output of it.

Best regards.


Feb, 2017 - Permalink

Thats the output from oracle developer:

http://oi64.tinypic.com/348rga0.jpg

The where statement shortens this one of one row down. Otherwise i had 10 with complete different spaces. (for example 40 MB)


Feb, 2017 - Permalink

Hi there,

Please shorten the "Free %" columns value to only 2 values after the comma (10,22% instead of 10,2321423424...%).

Does that work?

Best regards.


Feb, 2017 - Permalink

Yes. It works now. The result is 1:1 like in sql developer now.

So The old SQL oracle-V2 sensor dont like too long digits i suppose.

Thank you


Feb, 2017 - Permalink

Oh i thought i replied already. It worked btw.! The long comma value was the problem.


Feb, 2017 - Permalink