Health Monitor Run In Reactive Mode Even When There Are No Critical Errors

(Doc ID 2320492.1)

Last updated on NOVEMBER 01, 2017

Applies to:

Oracle Database - Enterprise Edition - Version 11.2.0.4 to 12.2.0.1 [Release 11.2 to 12.2]
Information in this document applies to any platform.

Goal

In general health monitor run in reactive mode in response to cricital errors on the database.

But in some scenarios the health monitor could run frequently in reactive mode even though there are no critical incidents

SQL>select * from v$hm_run order by start_time;

RUN_ID NAME CHECK_NAME RUN_MODE TIMEOUT START_TIME LAST_RESUME_TIME END_TIME MODIFIED_TIME STATUS SRC_INCIDENT NUM_INCIDENT ERROR_NUMBER PROBLEM_ID
1725761 HM_RUN_1725761 DB Structure Integrity Check REACTIVE 0 16-SEP-17 05.06.56.075461 PM 16-SEP-17 05.06.56.434470 PM 16-SEP-17 05.06.56.434470 PM COMPLETED 0 0 0 0
1725781 HM_RUN_1725781 DB Structure Integrity Check REACTIVE 0 16-SEP-17 05.16.56.542590 PM 16-SEP-17 05.16.56.865597 PM 16-SEP-17 05.16.56.865597 PM COMPLETED 0 0 0 0
1725801 HM_RUN_1725801 DB Structure Integrity Check REACTIVE 0 16-SEP-17 05.26.57.006463 PM 16-SEP-17 05.26.57.324859 PM 16-SEP-17 05.26.57.324859 PM COMPLETED 0 0 0 0
1725821 HM_RUN_1725821 DB Structure Integrity Check REACTIVE 0 16-SEP-17 05.36.57.534376 PM 16-SEP-17 05.36.57.846247 PM 16-SEP-17 05.36.57.846247 PM COMPLETED 0 0 0 0

 

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