Skip to main content

Executing A Load Plan

Load Plan 

A Load Plan is an executable object in Oracle Data Integrator that can contain a hierarchy of steps that can be executed conditionally, in parallel or in series. Procedures, interfaces, packages, variables, and can be added to Load Plans for executions in the form of scenarios in a Load Plan.
An ODI Load Plan is made up of a sequence of several types of steps. Each step can contain several small steps. Depending on the step type, the steps can be executed conditionally, in parallel, or sequentially. By default, an ODI Load Plan contains an empty root serial step. This root step is mandatory and the step type cannot be changed.

Creating a Load Plan 

ODI Load Plans appear in both the Designer and Operator Navigator. ODI Load Plans are available for edition in a development and production repositories, and can be organized into scenario folders.
"Right Click" and select "New" (Load Plan). Then specify a "Name" for the Load Plan.
ReddyVarun 2013 05 15 ODI ExecutingALoadPlan Image 1 resized 600 
Load Plan definition takes place on the "Steps Tab." You can define a hierarchy of steps in sequence/parallel conditionally based on the values of variables.
Data Warehouse Load Plan Example:
  • Dimensions are loaded in parallel. This includes the LOAD_TIME_DIM, LOAD_PRODUCT_DIM, LOAD_CUSTOMER_DIM scenarios, the geographical dimension and depending on the value of theODI_VAR_SESS1 variable, the CUST_NORTH or CUST_SOUTH scenario.
  • The geographical dimension consists of a sequence of three scenarios (LOAD_GEO_ZONE_DIM, LOAD_COUNTRIES_DIM, LOAD_CITIES_DIM).
  • After the dimensions are loaded, the two fact tables are loaded in parallel (LOAD_SALES_FACT andLOAD_MARKETING_FACT scenarios). 
ReddyVarun 2013 05 15 ODI ExecutingALoadPlan Image 2 resized 600  

Running a Load Plan

Run the ODI Load Plan by clicking the "Execute" button. The load plan running will be shown in the "Load Plan Executions" according to the Operator. Steps taken along with their status and statistics are shown in the"Steps Tab."  This tab reflects the executions in-progress and can be refreshed.
The sessions started by the load plan will still appear in the "Session's" list. However, the "Steps Tab" is more useful to monitor the overall execution of these sessions.
ReddyVarun 2013 05 15 ODI ExecutingALoadPlan Image 3 resized 600
Like 'Scenarios', ODI Load Plans can also be started from a command line or a web service interface. They can be scheduled using external scheduling or the built-in scheduler.
Load Plans require a JEE or Standalone agent for running. They cannot run within the Studio Local Agent. This is because the ODI Load Plan execution flow is distributed across the agents running the sessions started from the ODI Load Plan. Using this architecture, there is no single technical failure point that may prevent a load plan from proceeding its execution flow when the execution takes place on multiple agents.
Labels:

Comments

Post a Comment

Popular posts from this blog

ODI KM Adding Order by Option

You can add Order by statement to queries by editing KM.I have edited IKM SQL Control Append to provide Order by.  1) Add an option to KM named USE_ORDER_BY, its type is Checkbox and default value is False. This option determines you want an order by statement at your query. 2)Add second option to KM named ORDER_BY, type is Text. You will get order by values to your query by this option. 3) Editing Insert New Rows detail of KM. Adding below three line code after having clause. That's it! <% if (odiRef.getOption("USE_ORDER_ BY").equals("1")) { %> ORDER BY <%=odiRef.getOption("ORDER_BY" )%> <%} %>  If USE_ORDER_BY option is not used, empty value of ORDER_BY option get error. And executions of KM appears as such below; At this execution, I checked the KM to not get errors if ORDER_BY option value is null. There is no prove of ORDER BY I'm glad.  Second execution to get  Ord
99 comments
Read more

Creating Yellow Interface in ODI

Hello everyone! In Oracle data integrator (ODI), an  interface  is an object which populates one datastore, called the  target , with data coming from one or more other datastores, known as  sources . The fields of the source datastore are linked to those in the target datastore using the concept of  Mapping . Temporary interfaces used in ODI are popularly known as  Yellow Interfaces . It is because ODI generates a yellow icon at the time of creation of a yellow interface as opposed to the blue icon of a regular interface. The advantage of using a yellow interface is to avoid the creation of  Models each time you need to use it in an interface. Since they are temporary, they are not a part of the data model and hence don’t need to be in the Model. So let’s begin and start creating our yellow interface! Pre-requisites : Oracle 10g Express Edition with *SQL Plus, Oracle Data Integrator 11g. Open *SQL Plus and create a new table  Sales  in Oracle. You can use any existing ta
Post a Comment
Read more

Running Count in Talend Open Studio

Most Talend components keep a count of the records processed using variables like NB_LINE or NB_LINE_OK.  But these are only available after all processing is completed.  Define your own counter variable to keep a running count for use in a tMap. Variables like tFilterRow.NB_LINE or tAccessOutput.NB_LINE_INSERTED can be used to report the number of affected lines after a subjob's processing.  However, it may be of use to get the current line index for use in a tMap.  The index variables used to form NB_LINE aren't available during processing; they're only written out the globalMap at the end of processing. In this example, staging records are loaded from Excel to Access.  The order in which the Excel records are read is preserved in a database column called DISPLAY_SEQ_NB.  Note that there is an auto-increment column used for record ID in the Access table.  This could be used to infer a loading order, but this job uses a separate column to keep the ID as a meaningless surr
Post a Comment
Read more