ODI 12c OdiInvokeWebService Waits an Amount of Time Equal to -RETRY_INTERVAL_SECONDS Before First Execution
(Doc ID 2896819.1)
Last updated on AUGUST 07, 2024
Applies to:
Oracle Data Integrator on Marketplace - Version 12.2.1.4.220112 and laterOracle Data Integrator - Version 12.2.1.4.220112 and later
Information in this document applies to any platform.
Symptoms
The Oracle Data Integrator (ODI) 12c OdiInvokeWebService executes successfully when RETRY parameters are used, however, it takes an unjustified, significantly longer time than without RETRY parameters.
The issue can be reproduced at will with the following steps:
- Use ODI 12.2.1.4.220112 BP.
- Apply Patch 34202309 - OdiInvokeWebService fails when setting Retry on Error / Retry Interval
- Clear the ODI Studio cache.
- Start ODI Studio.
- In ODI Studio > Topology, create the appropriate Data server under "SOAP Web Service" technology.
Use a "WSDL URL" value that points to an accessible WebService, and using the appropriate credentials.
- In ODI Studio > Designer, create a Package which implements two OdiInvokeWebService steps to execute the above WebService:
- The first OdiInvokeWebService step should use the following parameters:
-RETRY_ON_ERROR
-RETRY_INTERVAL_SECONDS
- The second OdiInvokeWebService step should not use any of the above RETRY parameters.
- The first OdiInvokeWebService step should use the following parameters:
- Execute the Package using Local (No Agent), and observe:
- The first OdiInvokeWebService takes a long time, and succeeds after first attempt...
- The second OdiInvokeWebService takes a few seconds only, while it executes the same WebService...
Changes
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! |