16 Monitoring Jobs
In the Job Execution subtab of the Administration tab, you can query for and monitor any job submitted by any user. To perform the tasks in this chapter, you must have the LSH System Administrator functional role.
This chapter contains the following topics:
- About Execution in the Oracle Life Sciences Data Hub
Oracle LSH execution is based on the Oracle Warehouse Builder (OWB) runtime execution platform. - Querying for Jobs
You can view information on any job submitted by any user in the Administration tab. - Job Information
Some job information is available in the search results area at the bottom of the Job Administration screen. Additional information is available when you click the Job ID hyperlink for a particular job. - Job Statuses
Oracle Life Sciences Data Hub uses the following statuses to track the progress of a job. You must refresh the screen to see updates. - Execution Statuses
Execution statuses provide more detailed information than job statuses. For diagnostic purposes, the system displays the highest execution status a job reached, even if the job ended in failure.
About Execution in the Oracle Life Sciences Data Hub
Oracle LSH execution is based on the Oracle Warehouse Builder (OWB) runtime execution platform.
Oracle LSH passes every internal and user-submitted job to an OWB operator of the appropriate technology type. If OWB is down, Oracle LSH jobs do not run. Information on restarting OWB is included in Starting, Stopping, and Checking the Distributed Processing Service.
If the job requires execution by one of the integrated processing engines (such as SAS, Oracle Reports, or PL/SQL) Oracle LSH assigns the job to a service defined for that processing engine. The Oracle LSH Distributed Processing (DP) Server on the service location must be running for jobs of these types to run. Information about restarting the DP Server is included in Starting, Stopping, and Checking the Distributed Processing Service.
See "Execution and Data Handling" in the Oracle Life Sciences Data Hub Application Developer's Guide for additional information on execution and data handling in Oracle LSH. See "Using, Installing, and Cloning Work Areas" in the Oracle Life Sciences Data Hub Application Developer's Guide for information on Work Area installation.
Parent topic: Monitoring Jobs
Querying for Jobs
You can view information on any job submitted by any user in the Administration tab.
Jobs that you personally have submitted also appear in the Job Execution section of your My Home screen.
To query for one or more jobs, enter values in the following fields:
Click Clear to remove the search criteria and the search results in order to begin a new search.
Parent topic: Monitoring Jobs
Job Information
Some job information is available in the search results area at the bottom of the Job Administration screen. Additional information is available when you click the Job ID hyperlink for a particular job.
This section contains these topics:
- General Job Information
The system displays the following information about jobs in the search results at the bottom of the Job Administration screen: - Job Execution Details
If you click on the Job ID hyperlink in the Job Administration screen, the system opens the Job Execution Details screen.
Parent topic: Monitoring Jobs
General Job Information
The system displays the following information about jobs in the search results at the bottom of the Job Administration screen:
- Job ID
The system-generated ID of the job. You can click on the Job ID hyperlink to view execution details for the job. - Job Status
The current status of the job. - Name
The name of the executable object—Program, Load Set, Report Set, Workflow, or Data Mart—that generated the job. - Execution Setup
The name of the Execution Setup used to generate the submission form for the job. - Work Area
The name of the Work Area within which the job was executed. - Object Type
The object type of the executable that generated the job—Program, Load Set, Report Set, Workflow, or Data Mart. - Start TS
The timestamp of the beginning of the job. - End TS
The timestamp of the end of the job. - User
The user who submitted the job for execution.
Parent topic: Job Information
Job ID
The system-generated ID of the job. You can click on the Job ID hyperlink to view execution details for the job.
Parent topic: General Job Information
Job Status
The current status of the job.
See Job Statuses for further information.
Parent topic: General Job Information
Name
The name of the executable object—Program, Load Set, Report Set, Workflow, or Data Mart—that generated the job.
Parent topic: General Job Information
Execution Setup
The name of the Execution Setup used to generate the submission form for the job.
Parent topic: General Job Information
Work Area
The name of the Work Area within which the job was executed.
Parent topic: General Job Information
Object Type
The object type of the executable that generated the job—Program, Load Set, Report Set, Workflow, or Data Mart.
Parent topic: General Job Information
Job Execution Details
If you click on the Job ID hyperlink in the Job Administration screen, the system opens the Job Execution Details screen.
It displays the following information for the job:
- Submission Properties
The Job Execution Details screen includes values for the following properties in the upper portion of the screen: - Outputs
In the Outputs subtab, the system displays a row for each output generated by the job, if any. - Subjobs
If the job is the running of a Report Set or Workflow, it has subjobs. - Submission Parameters
Submission parameters are Parameters defined for the particular Program, Load Set, Report Set, Data Mart, or Workflow executed by the job. - System Parameters
System parameters are predefined for each object type. - Source Data Currency
The Source Data Currency subtab provides information on the most recent refresh of the data from all sources read by the job. - Log File
Click View Log to see the log file for the job.
Parent topic: Job Information
Submission Properties
The Job Execution Details screen includes values for the following properties in the upper portion of the screen:
- Job Name
The system generates a job name that includes the submission date and timestamp. - Job ID
The system-generated unique ID for the job. - Technology Type
The engine used to run the job concatenated with the object type that generated the job; for example, SAS Program or Text Data Mart. - Execution Status
The highest execution status the job has achieved. - Job Status
The current job status. - Error Message
If there is an error message associated with the job, a link to it appears here. - Validation Status
The validation status of the executable object instance used to generate the job. - Execution Setup
The name of the Execution Setup on which the submission form was based. - Execution User
The username of the person who submitted the job for execution. - Service Type
The type of service that ran the job. - Service Status
In Oracle Life Sciences Data Hub Release 2.4.8 this field always displays the status "Running." - Submission Time Stamp
The date and time the job was submitted for execution. - Start Time Stamp
The date and time the job execution started. - End Time Stamp
The date and time the job execution ended.
Parent topic: Job Execution Details
Job Name
The system generates a job name that includes the submission date and timestamp.
Parent topic: Submission Properties
Technology Type
The engine used to run the job concatenated with the object type that generated the job; for example, SAS Program or Text Data Mart.
Parent topic: Submission Properties
Execution Status
The highest execution status the job has achieved.
If the job is in progress, the status displayed is the current status. If the job has ended in failure or been aborted, the system displays the execution status the job had at the time it ended. See Execution Statuses for a complete list and description of each execution status.
Parent topic: Submission Properties
Job Status
The current job status.
See Job Statuses for a complete description of each job status.
Parent topic: Submission Properties
Error Message
If there is an error message associated with the job, a link to it appears here.
Parent topic: Submission Properties
Validation Status
The validation status of the executable object instance used to generate the job.
Parent topic: Submission Properties
Execution Setup
The name of the Execution Setup on which the submission form was based.
Parent topic: Submission Properties
Execution User
The username of the person who submitted the job for execution.
Parent topic: Submission Properties
Service Type
The type of service that ran the job.
See Service Types for a description of service types.
Parent topic: Submission Properties
Service Status
In Oracle Life Sciences Data Hub Release 2.4.8 this field always displays the status "Running."
Parent topic: Submission Properties
Submission Time Stamp
The date and time the job was submitted for execution.
Parent topic: Submission Properties
Outputs
In the Outputs subtab, the system displays a row for each output generated by the job, if any.
To view an actual output:
- Click the hyperlink in the Name column or the View icon next to it. The Output screen opens.
- Click View File.
- Choose to open or save the file.
In the Outputs subtab, the system displays the following information about each output:
- Title
The title is relevant only for primary outputs, which display the title. - Description
The Definer can enter a description of the output. - Primary Flag
The Primary Flag can be set to Yes or No and impacts the output. - Error Flag
If Error Flag is set to Yes, the output is an error file resulting from the job execution.
Parent topic: Job Execution Details
Title
The title is relevant only for primary outputs, which display the title.
By default the title is the same as the output's name. However, the Definer can specify a different title.
Parent topic: Outputs
Primary Flag
The Primary Flag can be set to Yes or No and impacts the output.
If Primary Flag is set to Yes, the output constitutes a primary reason for the job execution; it is a report on Oracle Life Sciences Data Hub data.
If set to No, the output is a log or error file produced as a result of running the job but not the primary reason for running the job.
Parent topic: Outputs
Error Flag
If Error Flag is set to Yes, the output is an error file resulting from the job execution.
Parent topic: Outputs
Subjobs
If the job is the running of a Report Set or Workflow, it has subjobs.
Note:
Program, Load Set, and Data Mart executions do not have subjobs.This section contains the following topics:
- Name
The name of the executable object—Program, Load Set, Report Set, Workflow, or Data Mart—that generated the subjob. - Type
The type of object that generated the subjob. - Job Status
The current job status of the subjob. - Execution Status
The highest execution status reached by the subjob. If the job is in progress, the status displayed is the current status.
Parent topic: Job Execution Details
Name
The name of the executable object—Program, Load Set, Report Set, Workflow, or Data Mart—that generated the subjob.
Parent topic: Subjobs
Job Status
The current job status of the subjob.
See Job Statuses for further information.
Parent topic: Subjobs
Execution Status
The highest execution status reached by the subjob. If the job is in progress, the status displayed is the current status.
If the job has ended in failure or been aborted, the system displays the execution status the job had at the time it ended.
Parent topic: Subjobs
Submission Parameters
Submission parameters are Parameters defined for the particular Program, Load Set, Report Set, Data Mart, or Workflow executed by the job.
This section contains the following topics:
- Name
The system displays the name of the Program, Load Set, Report Set, Data Mart or Workflow instance that was executed. - Type
The object type of the object listed in the Name column. - Value
The value in effect at submission.
Parent topic: Job Execution Details
Name
The system displays the name of the Program, Load Set, Report Set, Data Mart or Workflow instance that was executed.
Expand its node (+) to view the Parameters.
Parent topic: Submission Parameters
System Parameters
System parameters are predefined for each object type.
For further information, see the chapter on each object type in the Oracle Life Sciences Data Hub Application Developer's Guide.
This section contains the following topics:
- Name
The system displays the name of the Program, Load Set, Report Set, Data Mart or Workflow instance that was executed. Expand its node (+) to view the Parameters. - Type
The object type of the object listed in the Name column. - Value
The value in effect at submission.
Parent topic: Job Execution Details
Name
The system displays the name of the Program, Load Set, Report Set, Data Mart or Workflow instance that was executed. Expand its node (+) to view the Parameters.
Oracle Life Sciences Data Hub displays the name of the system parameter followed by its reference codelist.
Parent topic: System Parameters
Value
The value in effect at submission.
If a Parameter is not mandatory, it may have no value. When the allowed values are contained in a reference codelist, the system displays the name of the reference codelist surrounded by dollar signs, with the value at submission following. For example, where the value is $YESNO$YES
, the runtime value is Yes. The value Yes was selected from the YesNo reference codelist.
Parent topic: System Parameters
Source Data Currency
The Source Data Currency subtab provides information on the most recent refresh of the data from all sources read by the job.
Parent topic: Job Execution Details
Log File
Click View Log to see the log file for the job.
The log file includes information on the execution statuses the job attained. See Execution Statuses.
Parent topic: Job Execution Details
Job Statuses
Oracle Life Sciences Data Hub uses the following statuses to track the progress of a job. You must refresh the screen to see updates.
This section contains the following topics:
- Pending
The job has not yet started running. - Started
The job has begun pre-processing. - Executing
The Program has connected to database and is running. - Finalizing
The job has begun post-processing. - Success
The job has completed successfully without warnings. - Warnings
The job has completed successfully with warnings. - Failure
The job has completed with a fatal error. - Aborted
The job has been manually aborted. - On Hold
The job is waiting for the Work Area quiesce process to complete. - Expired
The system removed the job from the queue after the timeout interval passed. - Duplicate
The job is a duplicate of another job; the currency of the source data, parameter values, and executable instance version are the same.
Parent topic: Monitoring Jobs
On Hold
The job is waiting for the Work Area quiesce process to complete.
Parent topic: Job Statuses
Expired
The system removed the job from the queue after the timeout interval passed.
Parent topic: Job Statuses
Duplicate
The job is a duplicate of another job; the currency of the source data, parameter values, and executable instance version are the same.
Therefore the system does not rerun the job unless the person submitting the job chooses to force reexecution. To view the job that this one would duplicate, paste the Duplicate Job ID in the search window and locate the job.
Parent topic: Job Statuses
Execution Statuses
Execution statuses provide more detailed information than job statuses. For diagnostic purposes, the system displays the highest execution status a job reached, even if the job ended in failure.
This section contains the following topics:
- Submitted
Submitted is the initial execution status of the job on the job queue. - Initializing
The job is waiting for OWB operator processing to begin. - Serializing
The job is waiting for another instance of same program to complete. - Backchain
The system is performing backchain processing; examining the executable instances upstream to check if they have backchain Execution Setups defined and if so, if their source data is more current than their target data, and rerunning qualifying jobs as necessary to maximize data currency. - Recovering
The system is rolling back data written to tables in the previous execution of same program that did not complete successfully. - Pre-Execution Function
The system is executing a technology-specific pre-execution function. - Obtain Service
The system is obtaining a service instance appropriate for the Program's technology type and specified priority, given the service instances currently available for the technology type. - Pending Logon
The system is waiting for the Program to start and connect to the Oracle Life Sciences Data Hub database. - Executing
The Program has connected to the database and is executing. - Completing
The system is performing post-execution table completion processing. - Complete
The job has successfully completed processing. - Fail Backchain
The job failed during backchain processing. - Fail Logon
The job failed to connect to the Oracle Life Sciences Data Hub database. - Failed
The job failed at a phase not specified by one of the other failure statuses. - Rolling Back
The system is rolling back target tables to their pre-job state due to the job's execution failure. - Rolled Back
The system completed rolling back target tables to their pre-job state due to the job's execution failure.
Parent topic: Monitoring Jobs
Submitted
Submitted is the initial execution status of the job on the job queue.
This phase is required.
Parent topic: Execution Statuses
Initializing
The job is waiting for OWB operator processing to begin.
This phase is required.
Parent topic: Execution Statuses
Serializing
The job is waiting for another instance of same program to complete.
This phase is necessary only if the Program writes to target tables that require serialization. For further information, see "Data Processing Types" in the Oracle Life Sciences Data Hub Application Developer's Guide.
Parent topic: Execution Statuses
Backchain
The system is performing backchain processing; examining the executable instances upstream to check if they have backchain Execution Setups defined and if so, if their source data is more current than their target data, and rerunning qualifying jobs as necessary to maximize data currency.
This phase is required only for jobs specifying a data currency of Most Current Available. For a more complete description of backchaining, see "Backchaining" in the Oracle Life Sciences Data Hub Application Developer's Guide.
Parent topic: Execution Statuses
Recovering
The system is rolling back data written to tables in the previous execution of same program that did not complete successfully.
This phase is required only if the Program writes to targets and last job failed without recovering.
Parent topic: Execution Statuses
Pre-Execution Function
The system is executing a technology-specific pre-execution function.
This phase is required only by some technology types.
Parent topic: Execution Statuses
Obtain Service
The system is obtaining a service instance appropriate for the Program's technology type and specified priority, given the service instances currently available for the technology type.
This phase is required.
Parent topic: Execution Statuses
Pending Logon
The system is waiting for the Program to start and connect to the Oracle Life Sciences Data Hub database.
This phase is required for all jobs except Workflow master jobs.
Parent topic: Execution Statuses
Executing
The Program has connected to the database and is executing.
This phase is required.
Parent topic: Execution Statuses
Completing
The system is performing post-execution table completion processing.
This phase is required only if the Program writes to target tables.
Parent topic: Execution Statuses
Fail Logon
The job failed to connect to the Oracle Life Sciences Data Hub database.
Parent topic: Execution Statuses
Failed
The job failed at a phase not specified by one of the other failure statuses.
Parent topic: Execution Statuses
Rolling Back
The system is rolling back target tables to their pre-job state due to the job's execution failure.
Parent topic: Execution Statuses
Rolled Back
The system completed rolling back target tables to their pre-job state due to the job's execution failure.
Parent topic: Execution Statuses