|
Administration Guide for Oracle Billing Insight > Administering the Live Production Process >
Viewing and Verifying Task Status
Each production job consists of several individual tasks that work together to generate job output. In addition to job status, each individual task is assigned a status when the job runs. You can closely monitor and manage the task status for a job instance using the Command Center Task Status page. Every configured task must complete successfully before the application sets job status to Done on the Main Console. If any of the production tasks is unable to complete, then the job fails, and the status changes to Failed. All failed jobs display in red on the Main Console. If a job fails, then you can run it again. In addition to checking the individual task status on the Task Status screen, you can check for individual task output to determine whether a task completed successfully. To view task status detail for a job
- Click the status of the job in the Main Console Status column.
The Task Status screen appears showing the status of each production task in the job.
- To change the display order of tasks, click Task. To change the display order of information in the Last Run and Status columns, click Last Run or Status. Click the links again to restore each display to its original order.
Processing order remains unchanged.
- Click Refresh to display an updated task status.
- You have the option of rerunning or canceling a failed job. Click Retry Failed Job, or Cancel Failed Job.
- The Task Status page displays each instance of a job started during the most recent scheduled run in reverse chronological order with youngest first, along with the status of each task in the instance.
The Task Status page identifies each job instance by a Job Instance ID, and displays the information described in Table 59.
Table 59. Command Center Task Status Fields
|
|
Job Instance ID |
A number uniquely identifying each job instance. |
Last Updated |
The time the task status last updated. |
Status |
Current execution state of the task. Task Status can be: Processing, Failed, Reprocessing, Reprocess, No operation, Canceled, Not yet started, or Done. |
Action |
Displays an option that lets you take action on that job instance or on all instances. Retry lets you retry that instance. The Retry All option lets you retry all failed instances of the job. Cancel lets you cancel that instance. The Cancel All option lets you cancel all failed instances of the job. |
Which Job Instances Appear on the Task Status Page
The Task Status page displays:
- Up to the last N job instances that have Done, Canceled, or No operation status. In this task, N is the maximum number of instances allowed for the job.
- Any instances in Processing, Failed, Reprocessing, or Reprocess status
If you are not using concurrency (N=1), then the Task Status page shows up to five rows of job instances in Done, Canceled, or No operation status, plus any instances in Processing, Failed, Reprocessing, or Reprocess status. When a scheduled run completes, the completed rows remain in view on the Task Status page until a new schedule begins. At this point, the Task Status page begins displaying the instances generated by the new schedule instead. The only exception is that any instances from the previous schedule still in Processing, Failed, Reprocessing, or Reprocess states remain even if a new schedule has begun. Those instances are removed from the Task Status page once processing is complete, or in the case of a failed instance, once you cancel or retry it successfully. Schedules can overlap if a second schedule begins before the current run completes. Another scheduled run can begin only if:
- The first run is not using the maximum number of instances, if enough resource is available. For example, if the first run has 3 instances in Processing and the maximum allowed is 10, then the next run can start up to 7 new instances.
- No job instances in the first are in the Failed state.
Overlapping schedules mean that instances from both schedules could appear on the Task Status page. You can tell from the Last Updated field to which schedule the instance belongs.
The number of rows that appear on the Task Status page at any given time depends on the point of progress of the job and:
- Whether you have enabled concurrency for the job, if the maximum number of instances specified in the schedule is greater than 1.
- Represents the maximum number of Done, Canceled, or No operation jobs that can appear on the Task Status. The Task Status shows a maximum of 5 job instances in Done, Canceled, or No operation.
- For jobs that scan for an input file, the number of input files placed in the input directory.
- For jobs that process multiple statements in parallel with the StatementScanner task, such as the Report job, the number of statements to process up to the maximum number of instances.
- Whether the job schedule overlaps due to a long lasting run.
|
