My Oracle Support Banner

How To Implement A GO - NO GO Flag In ODI To Avoid Launching Multiple Parallel Executions Of The Same Scenario? (Doc ID 1138473.1)

Last updated on JUNE 28, 2016

Applies to:

Oracle Data Integrator - Version 10.1.3.5.6 and later
Information in this document applies to any platform.

Goal

An Oracle Data Integrator (ODI) Scenario is required to be launched frequently.

However, technical constraints require that there must be no overlap of execution and that an instance of the Scenario execution must determine if another instance is still running or not.

How to set up such an approach?

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!


In this Document
Goal
Solution
 Implement a GO - NO GO flag using a flat file and the OdiFileWait tool.
 Implement a GO - NO GO flag using an ODI Variable.
 Implement a GO - NO GO flag using an asynchronous restart of the job.
 Implement a GO - NO GO flag using a table as a placeholder for semaphores.
 Implement a GO - NO GO flag using an Oracle stored procedure, and the DBMS_LOCK package
References


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