Oracle Jobs Test
This test monitors Oracle jobs and reports the number of jobs that have failed and those that are broken. The detailed diagnosis capability offered by this test enables administrators perform further diagnosis on failed/broken jobs, by additionally revealing the complete details of the failed and broken jobs.
This test is disabled by default. To enable the test, go to the enable / disable tests page using the menu sequence : Agents -> Tests -> Enable/Disable, pick Oracle Database as the Component type, Performance as the Test type, choose this test from the disabled tests list, and click on the << button to move the test to the ENABLED TESTS list. Finally, click the Update button.
Target of the test : An Oracle server
Agent deploying the test : An internal agent
Outputs of the test : One set of results for every Oracle server.
|
Measurement | Description | Measurement Unit | Interpretation |
---|---|---|---|
Failed Oracle jobs |
Indicates the number of jobs that failed.
|
Number |
Ideally, the value of this measure should be 0. Any value greater than zero, is a cause of concern, as it indicates the existence of a failed job. To know which job(s) has failed, use the detailed diagnosis capability of this measure. Typically, if a job fails, Oracle attempts to run the job again 16 times, at fixed time intervals. You are advised to investigate the reason for the failure and fix it, by the time Oracle completes its 16th attempt. This is because, if the 16th attempt too fails, Oracle flags the job as a ‘broken job’, which can then be executed only manually. |
Broken Oracle jobs |
Indicates the number of jobs broken. |
Number |
Ideally, the value of this measure should be 0. Any value greater than 0 is a problem, as it indicates the existence of one/more broken jobs. A job is considered broken, only if the 16th attempt made by Oracle to run the job fails. To know which jobs have broken, use the detailed diagnosis capability of this measure. Once the jobs are identified, you can proceed to manually run the broken jobs through the DBMS_JOB.RUN procedure after logging in as the owner of that job. |
Running jobs |
Indicates the number of jobs that are currently running. |
Number |
The detailed diagnosis of this measure lists the Owner, Job name, Running instance, Session ID, CPU time, Elapsed time, Job Type, Repeat interval, Job start date, Job scheduled date and Job expire date. |
Maximum CPU time |
Indicates the maximum CPU time taken by a job during the last measurement period. |
Seconds |
A low value is desired for this measure. Use the detailed diagnosis of this measure to figure out the jobs that are taking the maximum CPU time. The detailed diagnosis of this measure lists the Owner, Job name, Status, Instance ID, Session ID, Serial number, CPU time, Elapsed time, Request start date, Log date, Error number and Additional info. |
Maximum elapsed time |
Indicates the maximum time taken for execution by a job during the last measurement period. |
Seconds |
A low value is desired for this measure. Use the detailed diagnosis of this measure to figure out the jobs that are taking too much of time for execution. The detailed diagnosis of this measure lists the Owner, Job name, Status, Instance ID, Session ID, Serial number, CPU time, Elapsed time, Request start date, Log date, Error number and Additional info. |
Successfully completed jobs |
Indicates the number of jobs that were successfully completed during the last measurement period. |
Number |
A high value is desired for this measure. Use the detailed diagnosis of this measure to figure out the jobs that were successfully completed. The detailed diagnosis of this measure lists the user who ran the job, the job number, job name, last execution date, next execution date and description of the job. |