219.You executed the following PL/SQL block successfully:
VARIABLE tname VARCHAR2(20)
BEGIN dbms_addm.insert_finding_directive (NULL, DIR_NAME=>'Detail CPU Usage',
FINDING_NAME=>'CPU Usage', 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
Answer: B
答案解析:
参考:http://docs.oracle.com/cd/E11882_01/appdev.112/e40758/d_addm.htm#ARPLS65063
INSERT_FINDING_DIRECTIVE Procedure
Creates a directive to limit reporting of a specific finding type.
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 INITIALstatus), 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); Parameters
Table 16-12 INSERT_FINDING_DIRECTIVE Procedure Parameters
ParameterDescription task_name
Name of the task this directive applies to. If the value is NULL, it applies to all subsequently created ADDM Tasks.
dir_name
Name of the directive. All directives must be given unique names.
finding_name
Name of an ADDM finding to which this directive applies. All valid findings names appear in the NAME column of view DBA_ADVISOR_FINDING_NAMES.
min_active_sessions
Minimal number of active sessions for the finding. If a finding has less than this number, it is filtered from the ADDM result.
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.
Examples
A new ADDM task is created to analyze a local instance. However, it has special treatment for 'Undersized SGA' findings. The result of GET_REPORT shows only an 'Undersized SGA' finding if the finding is responsiblefor at least 2 average active sessions during the analysis period, and this constitutes at least 10% of the total database time during that period.
var tname VARCHAR2(60);BEGIN DBMS_ADDM.INSERT_FINDING_DIRECTIVE( NULL, 'Undersized SGA directive', 'Undersized SGA', 2, 10); :tname := 'my_instance_analysis_mode_task'; DBMS_ADDM.ANALYZE_INST(:tname, 1, 2);END;To see a report containing 'Undersized SGA' findings regardless of the directive:
SELECT DBMS_ADVISOR.GET_TASK_REPORT(:tname, 'TEXT', 'ALL') FROM DUAL;
版权声明:本文为博主原创文章,未经博主允许不得转载。