Job Execution Problems

This section includes details on job execution issues and any possible workarounds.

It contains the following topics:

• Job Remains at Submitted or Executing
  If a job does not progress beyond a status of Submitted or Executing, try the steps in this section.
• Oracle Warehouse Builder Processes Do Not Start
  If Oracle Warehouse Builder (OWB) processes do not start, check the init.ora file for the setting of the job_queue_processes parameter.
• Job Runs But Does Not Upload Outputs
  If a job runs on an external engine (SAS, Oracle Reports, or XML Publisher) and generates outputs but doesn't upload the outputs to Oracle Life Sciences Data Hub, check the DP Server log.
• Job Log File Does Not Contain Info after a Long or Failed Execution
  If a job executes for a long time or fails and the job log does give enough information, check the Oracle Warehouse Builder (OWB) log.
• Job Fails to Obtain Service
  If a job that requires an external engine (SAS, Oracle Reports, or XML Publisher) fails at Obtainservice (or you get a No Data Found error at this point) run the script checkJSapps to see if the DP Server is running.
• Report Set Jobs Do Not Produce Any Output when using SAS 9.2
  If you are using SAS 9.2 and find that your Report Set jobs fail and do not generate any output, you must install the one-off patch 6993271.