Hi Henrik,
My knowledge of Oracle is not too much higher, but IMO you DBA is right. If the autoextend property is set on a tablespace, these cases should not cause a red status. I think the best way would be to check the Used size as a percentage of the "Autoextent(Size)" size, not the current "Size" size. I've experienced the same issue with BB's Oracle montoring scripts.
As a secondary monitoring point, disk monitoring should be enabled on the disks containing the tablespaces. They may well fill up before the max size is reached, preventing Oracle from extending the tablespaces to the maximum size allowed. Of course, if the Oracle data files do not reside on a filesystem, this cannot be done.
Cheers,
Eric.
Henrik Stoerner wrote:
I've started using Francesco's dbcheck script - very nice package, really. However, one of my DBA's is a bit unhappy with the tablespace check - it reports yellow/red status for tables that have been defined with AutoExtent enabled.
Right now I get a report like this:
Tablespace check (def. warning Use% >= 90%, def. alert Use% >= 95%) TableSpace/DBSpace Size Used Free Use% Autoextent(Size) BASIC_DATA2_1976_88 300.0M 215.0M 85.0M 72% YES (64.0G)
BASIC_DATA2_1989Q1 400.0M 382.0M 18.0M 96% YES (64.0G)
BASIC_DATA2_1989Q2 500.0M 483.0M 17.0M 97% YES (64.0G)with the last two tables causing a red status. My DBA thinks they should not trigger an alert, because they will automatically increase in size if needed.
Can anyone shed some light on this? My knowledge of Oracle is close to zero, so I really don't have any idea whether he is right or not.
Regards, Henrik
To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk