Interleaving of Scheduled ODI Scenarios May Result in Problems
(Doc ID 423855.1)
Last updated on AUGUST 07, 2024
Applies to:
Oracle Data Integrator - Version 10.1.3.2.0 and laterOracle Data Integrator Cloud Service - Version 17.1.3 and later
Data Integration Platform Cloud Classic - Version 17.3.5 and later
Oracle Data Integrator on Marketplace - Version 2.1.0 and later
Information in this document applies to any platform.
Symptoms
Oracle Data Integrator (ODI) Scenario executions have been scheduled to run hourly.
Also, an execution cycle has been defined, which results in Scenario looping:
- Many times, and
- An interval of 30 minutes between executions
Therefore, the total execution time of the cycle is greater than one hour; but each hour, a new schedule cycle is started. This implies that multiple instances of the same Scenario are running simultaneously and errors are signaled by ODI.
The following symptoms can be observed:
- In ODI Operator, it looks -- in the first few runs -- the jobs are following the specified interval (of 30 minutes), but after a few runs, the interval changes to seconds.
- The jobs sometimes fail with "Table or View does not exist" message.
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |