How to Unset Alert Thresholds Set via DBMS_SERVER_ALERT.SET_THRESHOLD (Doc ID 844035.1)

Last updated on DECEMBER 07, 2016

Applies to:

Enterprise Manager for Oracle Database - Version 10.1.0.4 to 11.1.0.7 [Release 10.1 to 11.1]
Information in this document applies to any platform.
***Checked for relevance on 07-Dec-2016***

Goal

After setting Alert threshold via DBMS_SERVER_ALERT.SET_THRESHOLD package, how can it be unset?

For example:

SQL> exec DBMS_SERVER_ALERT.SET_THRESHOLD( DBMS_SERVER_ALERT.CPU_TIME_PER_CALL, DBMS_SERVER_ALERT.OPERATOR_GE, '8000', DBMS_SERVER_ALERT.OPERATOR_GE, '10000', 1, 2, 'S102W6',DBMS_SERVER_ALERT.OBJECT_TYPE_SERVICE,'S102W6');

PL/SQL procedure successfully completed

SQL> SELECT metrics_name, warning_value, critical_value, consecutive_occurrences
FROM DBA_THRESHOLDS WHERE metrics_name LIKE '%CPU Time%';

METRICS_NAME                  WARNING_VA       CRITICAL_V        CONSECUTIVE_OCCURRENCES
-------------------------                  ----------                      ----------                   -----------------------
CPU Time Per User Call          8000                           10000                        2

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms