Managing Oracle's job queue from PATROL

Error rendering macro 'Include+'

The 'Include+' macro can only be used in spaces managed by Scroll Versions / Scroll Translations.

All 'Include+' and 'Excerpt Include+' macros must be converted to normal 'Include Page' and 'Excerpt Include' macros in such spaces.

Please use the macro conversion tool to detect and fix similar issues in this space or ask a space administrator to do so.

You can use PATROL to view and manage the job queue in the Oracle instance. You can run jobs manually, flag jobs as broken or not broken, and remove jobs from the job queue.

Before you can manage the job queue, you must activate the JOBS application by choosing KM Admin > Monitor Settings Modify from the INSTANCE menu, and enabling the JOBS category. You can also use this function to deactivate job queue monitoring.

The CollJobs parameter starts collecting information and populates the consumer parameters during the next polling cycle. The JOBS icon should appear within two polling cycles.

Note

The administrative and reporting menu commands are not supported for jobs scheduled with the DBMS_SCHEDULER package.

Viewing all jobs in the queue

To view all the jobs in the job queue, choose Reports > All Jobs from the JOBS menu or Reports > Jobs > All Jobs from the INSTANCE menu. All the jobs currently in the job queue are listed in the report, with the following information for each job:

All jobs report

Item	Description
Job Owner	name of the owner of the job
Job Number	number of the job
Broken	whether the job is broken or not
Failures	how many times the job failed to run
Job Definition	PL/SQL code that defines the job
Next Run	time when the job is set to run next

Finding failed jobs

A failed job is an Oracle task that has not executed properly 15 or fewer times (if it fails to execute properly 16 times in a row, it is flagged as a broken job). The FailedJobs parameter graphs the number of jobs that have failed to run. You can also run the Failed Jobs Report by choosing*Jobs > Failed Jobs* from the JOBS menu or Reports > Jobs > Failed Jobs from the INSTANCE menu.

The following table lists the information included in the Failed Jobs report.

Failed jobs report

Item	Description
Job Owner	name of the owner of the job
Job Number	number of the job
Broken	whether the job is broken or not
Failures	how many times the job failed to run
Job Definition	PL/SQL code that defines the job
Next Run	time when the job is set to run next

If a job fails to run 16 times in a row, it is flagged as broken, it is removed from the Failed Jobs Report, and it appears in the Broken Jobs Report.

Note

If you are monitoring an Oracle 8.0.4 database on an IBM ^® AIX ^® host, the Failed Jobs report might not correctly report the number of times that a job has failed to run. A column in the dba_jobs table in Oracle does not increment the number of times that a job fails. The FailedJobs parameter reflects this Oracle problem.

Finding overdue jobs

An overdue job is a job that is more then two minutes overdue. An overdue job may be a broken job or a failed job, or it may simply be blocked from running at its appointed time. The OverdueJobs parameter graphs the number of jobs that have not run at their proper time.

You can see all overdue jobs by choosing Jobs > Overdue Jobs from the JOBS menu or Reports > Jobs > Overdue Jobs from the INSTANCE menu. All overdue jobs are listed in a text window. The following table lists the information in the report.

Overdue jobs report

Item	Description
Job Owner	name of the owner of the job
Job Number	number of the job
Broken	whether the job is broken or not
Failures	how many times the job failed to run
Job Definition	PL/SQL code that defines the job
Next Run	time when the job is set to run next

Finding broken jobs

If a job has failed to run 16 times, it is automatically flagged as broken and does not run again. You can view all broken jobs by choosing Jobs > Broken Jobs from the JOBS menu or Reports > Jobs > Broken Jobs from the INSTANCE menu. All broken jobs are listed in the text window. The following table lists the information in the report.

Broken jobs report

Field	Description
Job Owner	name of the owner of the job
Job Number	number of the job
Failures	how many times the job failed to run
Job Definition	PL/SQL code that defines the job

Flagging jobs

You can manually flag a job as broken if you do not want the job to run again until you have corrected a problem. After you have corrected the problem, you can flag the job as not broken, and it will run again during its next scheduled execution time.

From the JOBS menu, choose Jobs > Flag Job > As Broken or Jobs > Flag Job > As Not Broken.
Select the user name of the owner of the job from the list, type the owner's password, and click OK.
Select one or more of the jobs that you want to flag, and click OK.
If no unbroken or broken jobs exist, the task output window displays a message saying that no unbroken or broken jobs exist.

Running jobs immediately

Use the following task to manually execute a job immediately. When you run a job manually from PATROL, Oracle attempts to execute the job even if the job has failed or is broken.

From the JOBS menu, choose Run Job.
Select the user name of the owner of the job from the list, type the owner's password, and click OK.
Select the job you want to run, and click OK.

Removing a job from the job queue

You can remove a job from the job queue, which prevents the job from being processed.

From the JOBS menu, choose Remove Job.
Select the user name of the owner of the job from the list, type the owner's password, and click OK.
Select the job you want to remove, and click OK.
You can remove all jobs that have not yet executed from the job queue. Jobs that you remove are not executed. However, you cannot remove a job that is currently executing. If you try to remove a job that is currently executing, the job is not interrupted and continues to execute.