Increase In Java Heap For ODI Standalone Agent Causes Crash For Scenarios
(Doc ID 1096035.1)
Last updated on JUNE 16, 2022
Applies to:Oracle Data Integrator - Version 10.1.3.5.6 and later
Information in this document applies to any platform.
We have first set up an Oracle Data Integrator (ODI) File Technology Data Server using the OPT property in the URL with a value of true:
After developing an ODI Integration Interface using a Datastore created from the above File Technology Data Server as Source, the related Scenario was repeatedly launched on the ODI standalone Agent.
When the Agents resources were audited using the jconsole tool as described in following Note:
<Note 1060081.1> - How To Track Java Memory Usage Using JConsole for ODI
the Threads window shows a constantly increasing number of active threads as time proceeds and results in resource saturation.
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