Best Practices for Context Independant Operations in ODI (Doc ID 424006.1)

Last updated on DECEMBER 08, 2023

Applies to:

Oracle Data Integrator - Version 3.2.03.01 and later
Oracle Data Integrator on Marketplace - Version 1.0.2 and later
Information in this document applies to any platform.

Goal

Case 1

A number of Oracle Data Integrator (ODI) 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

	To view full details, sign in with your My Oracle Support account.
	Don't have a My Oracle Support account? Click to get started!

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