You executed the following PL/SQL block successfully:
VARIABLE tname VARCHAR2(20)
BEGIN
dbms_addm.insert_finding_directive (NULL, DIR_NAME=>’Detail CPU Usage1,
FINDING_NAME=>’CPU Usage1,
MIN_ACTIVE_SESSIONS=>0,MIN_PERC_IMPACT=>90);
:tname := ‘database ADDM task4’;
dbms_addm.analyze_db(:tname, 150,162);
END;
/
Then you executed the following command:
SQL> SELECT dbms_addm.get_report(:tname) FROM DUAL;
The above command produces Automatic Database Diagnostic Monitor (ADDM) analysis____.
A.
with the CPU Usage finding if it is less than 90
B.
without the CPU Usage finding if it is less than 90
C.
with the CPU Usage finding for snapshots below 90
D.
with the CPU Usage finding for snapshots not between 150 and 162
http://docs.oracle.com/cd/E11882_01/appdev.112/e40758/d_addm.htm#ARPLS65061
INSERT_FINDING_DIRECTIVE Procedure
This procedure creates a directive to limit reporting of a specific finding type. The directive can be created for a specific task (only when the task is in INITIAL status), or for all subsequently created ADDM tasks (such as a system directive).
Syntax
DBMS_ADDM.INSERT_FINDING_DIRECTIVE (
task_name IN VARCHAR2,
dir_name IN VARCHAR2,
finding_name IN VARCHAR2,
min_active_sessions IN NUMBER := 0,
min_perc_impact IN NUMBER := 0);
min_perc_impact
Minimal number for the “percent impact” of the finding relative to total database time in the analysis period. If the finding’s impact is less than this number, it is filtered from the ADDM result.