An ODI Scheduled Scenario or Load Plan Is Launched Twice, Even if a Non-Clustered J2EE Agent Is Being Used
(Doc ID 2849653.1)
Last updated on MARCH 13, 2023
Applies to:
Oracle Data Integrator - Version 11.1.1.3.0 and laterOracle Enterprise Data Quality on Marketplace - Version 1.0.3 and later
Oracle Data Integrator Cloud Service - Version 17.1.3 and later
Data Integration Platform Cloud Classic - Version 17.3.5 and later
Information in this document applies to any platform.
Symptoms
A particular Scenario (or Load Plan) is scheduled to be executed by an Oracle Data Integrator (ODI) Agent daily, at 05:20 AM.
This configuration has been running for a considerable period of months and quite suddenly the same identical Scenario (or Load Plan) is launched twice with one minute (or a few seconds) interval.
Note the Schedule is set for execution on an ODI 11g or 12c non-clustered J2EE Agent, configured on one single Managed Server, without high availability to be involved, and without any other Servers defined in the Domain.
For example, in the screen copy above:
- Load Plan "001_..._LOAD_PLAN" is executed at 5:20:04 AM, and re-executed one minute later.
- Load Plan "001_..._DATA_LOAD_PLAN" is executed at 11:30:00 AM, and re-executed two seconds later.
For both the Load Plans above, only the first execution is intended, and respects the definition of Schedule.
The second execution is unintended.
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! |