ODI Jobs That Load to BAM Consumes More and More Memory from Server
(Doc ID 1143703.1)
Last updated on OCTOBER 19, 2023
Applies to:
Oracle Data Integrator - Version 10.1.3.5.6 and laterInformation in this document applies to any platform.
Symptoms
Using Oracle Data Integrator (ODI) 10.1.3.5.6, and running one scheduler Agent, with the following Java settings in the ODI "odiparams.sh" file:
The jobs are scheduled to run every n minutes. After a couple of days, the OS memory is used up and the OS user gets a Closed Connection error and can not log into the machine any more. The symptoms vary depending on the environment set up but mostly other symptoms are:
- ODI Agent dies with no error.
- the scheduled Scenario errors with java.lang.OutOfMemoryError: GC overhead limit exceeded
- Or Scenarios hang at RUNNING status forever.
It happens regardless which version of the Java is being used.
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! |
In this Document
Symptoms |
Cause |
Solution |
References |