About Execution

The Oracle Life Sciences Data Hub (Oracle LSH) offers the following capabilities related to execution and data handling:

• You can submit a job for immediate execution or schedule it for a later date and time or set it up to run at regular intervals; see Submitting Jobs for Execution.

• You can set up and run backchain execution to ensure that you are processing the most current data available in the source data system; see Backchaining.

• You can set up your source data system to send XML messages to trigger the execution of a job in CDR. NOTHING WRITTEN ON THIS AND NO INFO.

• If you are using Reload processing, you can choose to run in either Full or Incremental mode; use Incremental mode to quickly load and changed data; use Full mode to do the same and also to delete records that are not reloaded; see Reload Processing.

• Apply snapshot labels to the target or both source and target Table instances that a particular job reads from and writes to; see Data Snapshots.

• Maintain blinded data; see Managing Blinded Data.

Each job submitted from the user interface is called a master job. A master job may execute a single executable object, such as a Program, Load Set, or Data Mart. When a user submits a Report Set, the master job includes the execution of all the Program instances contained in the Report Set. A Workflow execution may include the execution of other executable objects. A Program execution using backchaining is also a master job that includes multiple subjobs.

Oracle LSH uses the runtime platform of the Oracle Warehouse Builder for all internal execution. Some additional information is available in "Stopping and Starting Services and Queues" in the Oracle Life Sciences Data Hub System Administrator's Guide.