When you edit the metric, you can add lines (originally there is only "All Others"). Add a line for your undo tablespace and use a > 100 or >= 101 as warning value, leave critical value blanc. Same for your temp tablespace.
Like UNDOTBS1 >= 101
and TEMP >= 101
Message was edited by:
If you use TEMP >=100 as Warning, this warning can still be raised.
What version of the database is it? If Oracle 10g, Grid Control (the agent) searches the alert table in the database for alerts, so the database raises the alert and the agent just passes this alert to Grid Control.
If you are using Oracle 10g, you can use the following statement (connected as sys):
metrics_id => DBMS_SERVER_ALERT.TABLESPACE_PCT_FULL,
warning_operator => DBMS_SERVER_ALERT.OPERATOR_GT,
warning_value => '90',
critical_operator => DBMS_SERVER_ALERT.OPERATOR_GT,
critical_value => '100',
observation_period => 1,
consecutive_occurrences => 1,
instance_name => NULL,
object_type => DBMS_SERVER_ALERT.OBJECT_TYPE_TABLESPACE,
object_name => 'TEMP');
This will create the GT (Greater Than) instead of GE (Greater Equal).
ps. I'm using GC 10.2.0.3.0, so thanks for the note that 10.2.0.4 doesn't take 100+ values.
I had this requirement as well.
I ended up writing my own notification method (Setup -> Notification methods). All alerts are run through this program, which has a table of events to ignore, escalate, or deprecate.
It's been working well.
Run this script in all databases where you need temp and undo alerts disabled.
cursor lc1 is select tablespace_name from dba_tablespaces where contents != 'PERMANENT';
FOR i IN lc1 loop
dbms_server_alert.operator_do_not_check, '0', 1, 1, NULL,
Query to verify at database level:
set pageisze 9999
set linesize 120
set numwidth 2
column metrics_name format a40
column object_name format a30
where metrics_name = 'Tablespace Space Usage';