Skip to main content

Using load plans in Oracle Data Integrator

Hello everyone!
Load plans were introduced in Oracle Data Integrator from version11.1.1.5.0. Load Plans are nothing but objects for organizing and launching scenarios in a production context.
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.
In this tutorial I will explain how to create a simple load plan in Oracle Data Integrator.
Pre-requisites: Oracle Data Integrator 11g (build version 11.1.1.7.0)
Step 1: Create a scenario
In this case I would be creating a scenario of one of my existing interfaces. You can refer this tutorial for creating a file to table load interface. Once you have created the interface, generate a scenario for the same.
Step 2: Create a load plan
Create a new load plan named TestLoadPlan1 by selecting Load Plans–> New Load Plan under the Designer navigator as follows!
load_plan_1
load_plan_2
Add a new Serial step named Serial. Then once again add a Serial step specifying the name of the task to be performed. Finally add a Scenario to this step for execution.
Validate the load plan if required and then execute it! :)
Note: In order to execute a load plan, you need to create a new stand alone agent in ODI. Refer this tutorial for more details. Make sure your agent is selected and running before you execute your load plan.
agent_running
Once you execute the plan, you should get a message saying “Load Plan started”. Check the status of the operation under the Operator tab. If the operation is successful, you should see the data in the target table! :)

load_plan_3
output
Labels:

Comments

  1. 21st Century Software Solutions30 September 2014 at 14:46:00 GMT+5:30

    Oracle Data Integrator Online Training, ONLINE TRAINING – IT SUPPORT – CORPORATE TRAINING http://www.21cssindia.com/courses/oracle-data-integrator-online-training-125.html The 21st Century Software Solutions of India offers one of the Largest conglomerations of Software Training, IT Support, Corporate Training institute in India - +919000444287 - +917386622889 - Visakhapatnam,Hyderabad Oracle Data Integrator Online Training, Oracle Data Integrator Training, Oracle Data Integrator, Oracle Data Integrator Online Training| Oracle Data Integrator Training| Oracle Data Integrator| "Courses at 21st Century Software Solutions
    Talend Online Training -Hyperion Online Training - IBM Unica Online Training - Siteminder Online Training - SharePoint Online Training - Informatica Online Training - SalesForce Online Training - Many more… | Call Us +917386622889 - +919000444287 - contact@21cssindia.com
    Visit: http://www.21cssindia.com/courses.html"

    ReplyDelete

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