Batch Run Tree - Main
This page allows you to view the status of a specific execution of a batch job. Navigate to this page using > > .
Description of Page
Select a Batch Control process and Batch Number to view information and statistics on the batch run's "threads". The following points should help understand this concept:
• Many batch jobs cannot take advantage of your hardware's processing power when they are run singularly. Rather, you'll find that a large percentage of the CPU and/or disk drives are idle.
• In order to minimize the amount of idle time (and increase the throughput of your batch processes), we allow you to set up your batch processes so that multiple instances of a given batch job are executed at the same time. For example, in Oracle Utilities Customer Care and Billing when you schedule the billing process, you can indicate that multiple parallel instances should be executed (rather than just one instance). You'd do this so that the processing burden of creating bills for your customers can be spread over multiple processes.
• We refer to each parallel execution of a batch process as a "thread".
• Statistics and information messages are displayed in respect of each thread. Why? Because each thread is a separate execution and therefore can start and end at different times.
The Start Date/Time and End Date/Time of the batch run are shown.
The tree includes a node that displays the total number of records processed for the batch run, the total number of records in error for the batch run and the batch run elapsed time. The elapsed time is the longest elapsed time among the batch thread(s). The message is red if there are any records in error. Within each thread, a node appears for each batch instance for the thread. A thread will only have more than one instance in the case of a thread that ended in error where a user subsequently restarted the run. The Start Date/Time and End Date/Time of the batch run are shown, if populated.
The messages that appear under a thread instance show the start and end times of the execution instance. If errors are detected during the execution of the thread, these error messages may also appear in the tree. Refer to
Processing Errors for information about the types of errors that appear in the batch run tree.
If the background process has been enabled to create
To Do entries for object specific errors, information about the To Do entries are displayed in the tree. This information is not displayed for each thread, but rather all the To Do entries created for the batch run are grouped together. The To Do entries are grouped by their status.
If the application properties file has been configured with the location of the log files and the log files associated with the batch thread are still available, the links Download stdout and (if applicable) Download stderr are visible. Clicking either link allows you to view or save the log files.
Note:Compression. The log files are compressed and include a *.gz extension. Different browsers treat this type of file differently. Some browsers may automatically decompress the file as part of the download and they are viewable in any text viewer by changing the extension to one the text viewer recognizes. However, some browsers download the compressed file and a user will need to unzip the file prior to viewing.
Note:Security Access. The 'download' hyperlinks are only visible for users that have security access to the Download access mode for the batch run tree application service.
Parent topic