1

Topic: Automatic Report Capturing

Came across on High CPU Usage and/or Frequent Occurrences of ORA-12850 For Monitor Queries by MMON From 12.1 (Doc ID 2102131.1) . About Automatic Report Capturing any . Whether interests, at least, there is a possibility a the schedule for Automatic Report Capturing instead of e as it does _report_capture_cycle_time.
SY.

2

Re: Automatic Report Capturing

SY;
Apparently, it is necessary to ungear at first, and then to switch on and off through DBMS_AUTO_REPORT.start_report_capture , DBMS_AUTO_REPORT.finish_report_capture

3

Re: Automatic Report Capturing

Only important difference - at automatic will be regular:

SQL> select execution_mode, last_cycle_time, sysdate from v$sys_report_stats;
EXECUTION_MO LAST_CYCLE_TIME SYSDATE
------------ ------------------- -------------------
REGULAR 2017-11-22 3:58:14 PM 2017-11-22 3:58:18 PM

and at DBMS_AUTO_REPORT.start_report_capture will be FULL_CAPTURE:

SQL> exec DBMS_AUTO_REPORT.start_report_capture;
PL/SQL procedure successfully completed.
SQL> select execution_mode, last_cycle_time, sysdate from v$sys_report_stats;
EXECUTION_MO LAST_CYCLE_TIME SYSDATE
------------ ------------------- -------------------
FULL_CAPTURE 2017-11-22 3:56:13 PM 2017-11-22 3:57:52 PM

4

Re: Automatic Report Capturing

Thanks. .e. Explicitly in any way. We stop through DBMS_AUTO_REPORT.finish_report_capture. We launch in due time through DBMS_AUTO_REPORT.start_report_capture and after that it is fulfilled through everyone _report_capture_cycle_time seconds after the termination previous. Though, basically it is possible to install in due time simply _report_capture_cycle_time and how many DBMS_AUTO_REPORT.start_report_capture once a minute that an error quite comprehensible is fulfilled.
SY.

5

Re: Automatic Report Capturing

SY;
Only there is a difference between REGULAR and FULL_CAPTURE that is visible even on titles: at FULL_CAPTURE  saves generally all that is in v$sql_monitor, and at REGULAR only at "the big loading".
Remaining parameters:

SQL> @param_ report_cap
NAME VALUE TYPE DESCRIPTION
-------------------------------------- ------- ------- ------------------------------------------------------------
_report_capture_cycle_time 0 number Time (in sec) between two cycles of report capture daemon
_report_capture_dbtime_percent_cutoff 50 number 100X Percent of system db time daemon is allowed over 10 cycles
_report_capture_recharge_window 10 number No of report capture cycles after which db time is recharged
_report_capture_timeband_length 1 number Length of time band (in hours) in the reports time bands table