5 ODI Execution
Perform bulk data transformations using Scenarios created in ODI Studio.
What is ODI Execution?
This task enables you to perform bulk operations and transformations.
The ODI Execution Task enables you to run Scenarios created in Oracle Data Integrator (ODI) Studio, and then monitor them centrally in Data Integration Platform Cloud.
See, Using Scenarios to learn more about Scenarios.
What’s Certified for ODI Execution?
Review the supported agents, data sources, and limitations before choosing your source and target for ODI Execution.
Note:
-
All data sources must have x86_64, the 64 bit version of x86 operating systems, with the latest upgrade.
-
Flat files located on all operating systems and versions can work for ODI Execution.
-
SQL Server is only certified on Windows.
| Connection type | Version | OEL | RHEL | SLES | Windows | Source | Target |
|---|---|---|---|---|---|---|---|
|
Autonomous Data Warehouse Cloud |
18.1 |
6.x |
6.x, 7.x |
11, 12 |
no |
no |
yes |
|
Oracle Database Cloud Classic |
12.2 |
6.x |
no |
no |
no |
yes |
yes |
|
Oracle Database Cloud Classic |
12.1 |
6.x |
no |
no |
no |
yes |
yes |
|
Oracle Database Cloud Classic |
11.2 |
6.x |
no |
no |
no |
yes |
yes |
|
Oracle Database |
12.2 |
6.x |
6.x, 7.x |
no |
no |
yes |
yes |
|
Oracle Database |
12.1 |
6.x |
6.x, 7.x |
no |
no |
yes |
yes |
|
Oracle Database |
11.2.0.4 |
6.x |
6.x, 7.x |
no |
no |
yes |
yes |
|
Oracle Object Storage |
n/a |
n/a |
n/a |
n/a |
n/a |
yes |
yes |
|
SQL Server |
2016 EE (SP2) |
no |
no |
no |
2016 |
yes |
yes |
|
SQL Server |
2016 EE (SP1) |
no |
no |
no |
2016 |
yes |
yes |
|
SQL Server |
2014 EE |
no |
no |
no |
2012 |
yes |
yes |
|
SQL Server |
2012 EE |
no |
no |
no |
2012 |
yes |
yes |
|
MySQL |
5.x |
no |
6.x, 7.x |
no |
no |
yes |
yes |
|
Flat Files |
n/a |
yes |
yes |
yes |
yes |
yes |
yes |
After you verify your data source operating systems and versions, you must set up agents only for the data sources that are certified for your tasks. Ensure that you install agents on certified operating systems and that the agents can connect to your data sources. See Agent Certifications.
What are the Limitations for ODI Execution?
The following are limitations of the ODI Execution Task:
-
If you run multiple tasks with the same agent at the same time, the tasks may take longer to execute.
-
You can only import Patch Deployment Archives. Other deployment archive types such as Execution Deployment Archives are not supported.
Before You Create an ODI Execution Task
To perform an ODI Execution Task in Data Integration Platform Cloud, you need to download and set up your Agent, and create your Connections.
Set up a Scenario
Using ODI Studio, set up a Scenario. You may also need a deployment archive if you want to import the Scenarios into Data Integration Platform Cloud.
For more information, see Using Scenarios.
Set up a Remote Agent
Create Connections
Create an ODI Execution Task
Creating an ODI execution task requires general information like name and description of the task.
To create an ODI Execution Task:
-
In the Getting Started section of the Home page, click Create for ODI Execution, or click Create in the Catalog, select ODI Execution.
-
In the Edit ODI Execution Task screen:
-
Under the General Information section, enter a name and description for this task.
-
Go to the Connections section:
-
Scenario Name: Select a scenario you want to execute. Click Import to select a scenario from a patch deployment archive created in ODI Studio.
- Logical Schema-
The logical schemas that are used for source and target connectivity in ODI Studio. Click Add Connection (the plus sign), which appears by clicking on the corresponding row, to create multiple connections.
- Select the appropriate Connection and the Schema.
-
-
-
Click Save to save the task or click Save and Run to save and start the ODI Execution job, which brings you to the job page where you can monitor your job.