Best Practices For Context Independant Operations In ODI (Doc ID 424006.1)

Last updated on OCTOBER 04, 2022

Applies to:

Goal

Case 1

A number of Oracle Data Integrator Scenarios have been developed which make use of  ODI Variables.

The refresh statement of these variables is typically as follows:

How is it possible to ensure that the Variables will be correctly refreshed in other ODI Contexts?

Case 2

The ODI OdiSqlUnload tool  has a hard-coded -FILE parameter (for example: c:\temp\myfile.txt).

In other Execution Contexts, this parameter will have other values even if the file name itself remains unchanged (for example: /home/files/myfile.txt).

Is it possible to make this parameter independent from the Execution Context?

Solution

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.