-
Title
Rule "DBO - Job Broken" does not fire an alarm -
Description
Some of the Oracle jobs are failing but Foglight did not send an alarm.
-
Cause
This alarm is invoked when a job is either in "Broken" status or "Disabled" state (the disabled state is relevant only for scheduler jobs). A job can become broken in one of the following conditions:
In case of a scheduler job if the number of failed attempts to run exceeds a predefined threshold (max_failures attribute).
In case of a dbms_job - if the status is explicitly set to Broken by the user (using the DBMS_JOB.BROKEN procedure) or has been marked as Broken by Oracle.
In Oracle12C and higher versions this alarm can also be invoked at the PDB level.
-
Resolution
Make sure the Oracle parameter max_failures is set properly, so that the alarm can be triggered.
From the Oracle documentation:
A broken job is one that has exceeded a certain number of failures. This number is set in max_failures, and can be altered. In the case of a broken job, the entire job is broken, and it will not be run until it has been fixed.More details on max_failure can be found under Oracle page: http://docs.oracle.com/database/121/SBYDB/log_arch_dest_param.htm#i77878