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.